Skip to content
External endpointresponds

DiscreteRate

Run DRS demos (Fast-Slow Drain, Hamburger Duo, Valdez Tanker) and explore the paradigm.

Endpoint URL
https://discreterate.com/mcp/v1
Current status
responds
Last checked
Aug 17, 2026, 05:01 AM UTC
Check
MCP initialize · 8s limit
Latency
170 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.discreterate/public

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
discreterate-v1
Version
1.5.0
Capability keys
tools
Tool names
run_fast_slow_drain, run_hamburger_duo, run_valdez_tanker, run_vegetable_plant, run_chocolate_processing, run_sku_capacity, run_tissue_line, list_drs_demos, describe_demo, explain_discrete_rate_simulation, explain_three_primitives, explain_paradigm_integration, explain_des_vs_drs_event_complexity, run_showcase
Instructions excerpt

DiscreteRate's public MCP. Two kinds of tool: (1) VERIFIED-REFERENCE tools — the seven run_* sim tools (Fast-Slow Drain, Hamburger Duo, Valdez Tanker, Vegetable Plant, Chocolate Processing, Bottling Line SKU capacity, Tissue Line) return canonical curated numbers from real DRS engine runs, and five explain_*/catalog tools return educator-flavored prose. (2) run_showcase (present only when the live engine is wired in) runs the real engine LIVE for parameters you choose and returns its verbatim run envelope — real output for that exact configuration, NOT a canonical reference number. ANTI-FABRICATION: quote every returned number verbatim; do not round, estimate, average, or recall figures from training data. Keep the two contracts distinct — present run_showcase output as a live experiment result and the run_* tools' numbers as canonical reference; never blend them. For a follow-up about a run you did earlier, re-call the tool rather than recalling numbers from chat history.

Reported Aug 17, 2026, 05:01 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 148ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 276ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 202ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 170ms