DiscreteRate MCP
A public MCP server that allows AI assistants to connect to ReliaSim's discrete rate simulation engine. It enables users to run demos, explore simulation paradigms like Fast-Slow Drain, and access curated reference results from saved engine runs to analyze production throughput, bottlenecks, and supply chain decisions.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://discreterate.com/mcp/v1What its tools do
14 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to discreterate.com ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Run DRS demos such as Fast-Slow Drain and Hamburger Duo
- Explore the discrete rate simulation paradigm
- Connect AI assistants to ReliaSim's public MCP endpoint
- Access curated reference results from saved engine runs
Source and maintenance
- Maintenance checked
Protocol and capabilities
- Server
- discreterate-v1 1.5.0
- MCP protocol negotiated in check
- 2025-06-18
- Tools
- 14 advertised
- Resources
- Not advertised
- Resource templates
- Not advertised
- Prompts
- Not advertised
{
"tools": {
"listChanged": false
}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
14 advertised
run_fast_slow_drain — Run Fast-Slow Drain (Damiron-Nastasi 2008)
Run the Fast-Slow Drain (FSD) demo — Damiron-Nastasi 2008 oscillating tank. The canonical DRS-vs-DES event-count demonstration. Returns engine output including the event counts (DES vs DRS), tank-level trace, and cycle summary. ANTI-FABRICATION: numbers come from a real DRS engine run; quote verbatim, don't recall from training data.
{
"type": "object",
"properties": {
"simulation_minutes": {
"type": "integer",
"default": 100,
"maximum": 1000,
"minimum": 10,
"description": "Total simulation horizon in minutes. Default 100. Range 10-1000."
}
}
}{
"title": "Run Fast-Slow Drain (Damiron-Nastasi 2008)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}run_hamburger_duo — Run Hamburger Duo (Siprelle, DES + DRS side-by-side)
Run the Hamburger Duo (HAM) demo — Andy Siprelle's 5-stage finite-source line, executed as both DES and DRS implementations on the same model so the event-count and throughput numbers can be compared apples-to-apples. Returns engine output for the side-by-side run. ANTI-FABRICATION: numbers come from a real engine run; quote verbatim.
{
"type": "object",
"properties": {
"simulation_days": {
"type": "integer",
"default": 7,
"maximum": 30,
"minimum": 1,
"description": "Days to simulate. Default 7. Range 1-30."
}
}
}{
"title": "Run Hamburger Duo (Siprelle, DES + DRS side-by-side)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}run_valdez_tanker — Run Valdez Tanker (Koelling-Remy 1983)
Run the Valdez Tanker (VALD) demo — Koelling-Remy 1983 Alaska Pipeline model, the paradigm-integration motivator. Crude flows continuously into the Valdez Marine Terminal storage tank (Flow); tankers arrive discretely to drain it (Item); DRS handles both via F2I / I2F transitions. Returns engine output including tanker arrival/departure events and tank-level trace. ANTI-FABRICATION: numbers come from a real engine run; quote verbatim.
{
"type": "object",
"properties": {
"simulation_days": {
"type": "integer",
"default": 30,
"maximum": 90,
"minimum": 1,
"description": "Days to simulate. Default 30. Range 1-90."
}
}
}{
"title": "Run Valdez Tanker (Koelling-Remy 1983)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}run_vegetable_plant — Run Vegetable Plant (Plant Builder distribution control)
Run the Vegetable Plant (VEG) demo — a Plant Builder distribution-control model. Two Making lines feed five Packing lines through eight surge bins; a DRS rate solver splits and rebalances the flow across the bins as the plant works through its campaign schedule. Returns the plant rollup (utilization, campaigns, active window), per-product goal attainment, per-system campaign timelines, and final surge-bin / delivered levels. ANTI-FABRICATION: numbers come from a real Plant Builder engine run; quote verbatim.
{
"type": "object",
"properties": {}
}{
"title": "Run Vegetable Plant (Plant Builder distribution control)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}run_chocolate_processing — Run Chocolate Processing (Plant Builder DES↔DRS bridge)
Run the Chocolate Processing (CHOC) demo — Plant Builder's joint DES↔DRS bridge. Three systems in series (Bean Processing → Cocoa Powder → Chocolate): DES schedules campaigns and injects equipment failures, a DRS rate solver carries the continuous flow, a bridge couples them. Exercises all 7 controllers + Goal blocks. Returns the plant rollup (schedule occupancy vs busy utilization, total downtime, campaigns), per-product attainment, and per-system campaign timelines with downtime. ANTI-FABRICATION: numbers come from a real Plant Builder engine run; quote verbatim.
{
"type": "object",
"properties": {}
}{
"title": "Run Chocolate Processing (Plant Builder DES↔DRS bridge)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}run_sku_capacity — Run Bottling Line SKU capacity
Run the Bottling Line / SKU-capacity (SKU) demo — a sim-foundation parameter-set example. One 5-machine bottling line run for several products (SKUs as parameter sets). Returns, per SKU, OEE (identical ~55% — time-based interrupts) and indexed real output (swings >3x: 100 / 50 / 30 / 42) plus the pacing machine. Shows you can't read per-SKU capacity off OEE. ANTI-FABRICATION: numbers come from a real sim-foundation engine run (indexed/anonymized); quote verbatim.
{
"type": "object",
"properties": {}
}{
"title": "Run Bottling Line SKU capacity",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}run_tissue_line — Run Tissue Line strategic decision
Run the Tissue Line (TIS) demo — a sim-foundation parameter-set example. One tissue line (Reel supply → Converter → Winder), three strategic decisions (each a parameter set): bypass converter / run converter / add storage tower. Returns per-decision throughput as % of nameplate (75.4 / 75.4 / 73.4), the binding bottleneck (the upstream parent-reel supply in all three), and converter/storage detail. Shows the downstream decision barely moves throughput — invest at the constraint. ANTI-FABRICATION: numbers come from a real sim-foundation engine run (indexed/anonymized); quote verbatim.
{
"type": "object",
"properties": {}
}{
"title": "Run Tissue Line strategic decision",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}list_drs_demos — List DRS canonical demos
List the seven DRS demos (Fast-Slow Drain · Hamburger Duo · Valdez Tanker · Vegetable Plant · Chocolate Processing · Bottling Line SKU capacity · Tissue Line). Each is reproducible against the engine via the run_* tools. Use this to discover what's available before calling describe_demo or a run_* tool.
{
"type": "object",
"properties": {}
}{
"title": "List DRS canonical demos",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}describe_demo — Describe one DRS demo
Full per-demo write-up: history, what it teaches, what to expect from the run_* output. Use this to ground the user before triggering a sim run, or to explain WHY the demo exists when the user asks a conceptual question about it.
{
"type": "object",
"required": [
"demo"
],
"properties": {
"demo": {
"enum": [
"fast_slow_drain",
"hamburger_duo",
"valdez_tanker",
"vegetable_plant",
"chocolate_processing",
"sku_capacity",
"tissue_line"
],
"type": "string",
"description": "Which DRS demo to act on. See list_drs_demos for the catalog."
}
}
}{
"title": "Describe one DRS demo",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}explain_discrete_rate_simulation — DRS paradigm primer
Return a textbook-tier explainer of Discrete Rate Simulation: how it differs from DES and CT, the three primitives (Constraint / Buffer / Interrupt), paradigm integration via F2I / I2F. Use this for 'what is DRS?' / 'how is this different from DES?' / 'where does DRS fit in the simulation landscape?' style questions. Deterministic text — no engine call, no RNG.
{
"type": "object",
"properties": {}
}{
"title": "DRS paradigm primer",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}explain_three_primitives — Three primitives primer
Return a focused write-up of the three DRS modeling primitives: Constraint (rate-limiter), Buffer (accumulated state), Interrupt (stoppage). Use this when the user asks specifically about modeling primitives or how to spell a system in DRS. Deterministic text.
{
"type": "object",
"properties": {}
}{
"title": "Three primitives primer",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}explain_paradigm_integration — F2I / I2F integration primer
Return an explainer of paradigm integration — how DRS handles systems with both flows and items via F2I (Flow-to-Item) and I2F (Item-to-Flow) primitives. Use this when the user asks about Valdez-Tanker-style mixed-paradigm systems or 'how do flows and items coexist'. Deterministic text.
{
"type": "object",
"properties": {}
}{
"title": "F2I / I2F integration primer",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}explain_des_vs_drs_event_complexity — DES vs DRS event-count primer
Return a focused write-up of the event-count complexity differences between DES and DRS, with the worked Fast-Slow Drain numbers (Continuous ~thousands vs DES ~500 vs DRS 10 events for the same 100-minute model). Use this when the user wants the practitioner-visible payoff of DRS — the 50× event-count reduction at the boundary-transition layer. Deterministic text.
{
"type": "object",
"properties": {}
}{
"title": "DES vs DRS event-count primer",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}run_showcase — Run a DRS demo live (your parameters)
LIVE EXPERIMENT — run a DRS demo against the real engine with parameters you choose, and get its verbatim run envelope (metadata, execution stats, metrics, details). This is the only tool that COMPUTES fresh output: pick a demo_id and dial its knobs (e.g. `stop_time` run length, or the MTBF/MTTR/goal knobs on the plant demos) to see the real numbers for that exact configuration. IMPORTANT: a run_showcase result is NOT a verified reference number — unlike the run_* tools (run_fast_slow_drain / run_hamburger_duo / run_valdez_tanker / run_vegetable_plant / run_chocolate_processing), which return curated, canonical reference values. Present run_showcase output as a live experiment result for the parameters passed; don't blend it with the curated reference numbers. Quote any figures verbatim; do not round, average, or derive.
{
"type": "object",
"required": [
"demo_id"
],
"properties": {
"knobs": {
"type": "object",
"description": "Optional parameters as a map of name:number. fast_slow_drain / hamburger_duo accept `stop_time` (run length in minutes, 1–100000). valdez_tanker accepts `duration_days` (run length in days, 1–365; it drives the circulating-ship items loop). vegetable_full accepts `making_goal` (units, 0–100000), `making_mtbf` / `making_mttr` / `packing_mtbf` / `packing_mttr` (hours, 0–1000). chocolate_processing accepts `bp_goal` (units, 0–100000), `breaker_mtbf` / `breaker_mttr` (hours, 0–1000), `changeover_delay` (hours, 0–48). Unknown names are rejected; out-of-range values are clamped by the engine."
},
"demo_id": {
"enum": [
"fast_slow_drain",
"hamburger_duo",
"valdez_tanker",
"vegetable_full",
"chocolate_processing"
],
"type": "string",
"description": "Which DRS demo to run live against the real engine."
}
}
}{
"title": "Run a DRS demo live (your parameters)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}Prompts
Not advertised
Resources
Not advertised
90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-06: 1 of 1 checks answered
- 2026-11-07: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 455 ms
- 95th percentile latency
- 455 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 455 ms · metadata changed · 14 tool(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http discreterate-mcp https://discreterate.com/mcp/v1Codex
codex mcp add discreterate-mcp --url https://discreterate.com/mcp/v1Cursor
{
"mcpServers": {
"discreterate-mcp": {
"url": "https://discreterate.com/mcp/v1"
}
}
}Cline
{
"mcpServers": {
"discreterate-mcp": {
"type": "streamableHttp",
"url": "https://discreterate.com/mcp/v1",
"disabled": false
}
}
}VS Code
{
"servers": {
"discreterate-mcp": {
"type": "http",
"url": "https://discreterate.com/mcp/v1"
}
}
}Gemini CLI
gemini mcp add --transport http discreterate-mcp https://discreterate.com/mcp/v1Claude Desktop
https://discreterate.com/mcp/v1Windsurf
{
"mcpServers": {
"discreterate-mcp": {
"serverUrl": "https://discreterate.com/mcp/v1"
}
}
}Let your agent find its tools
Find servers like DiscreteRate MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other data and analytics servers
Do you run DiscreteRate MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.