DiscreteRate
REMOTE · DISCRETERATE.COM · SCANNED SEP 21
Run DRS demos (Fast-Slow Drain, Hamburger Duo, Valdez Tanker) and explore the paradigm.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2003 tokens (~143/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the DiscreteRate MCP server?
DiscreteRate is a hosted endpoint at https://discreterate.com/mcp/v1, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · discreterate.com
claude mcp add --transport http com-discreterate-public 'https://discreterate.com/mcp/v1'
{
"mcpServers": {
"com-discreterate-public": {
"url": "https://discreterate.com/mcp/v1"
}
}
} {
"servers": {
"com-discreterate-public": {
"type": "http",
"url": "https://discreterate.com/mcp/v1"
}
}
} [mcp_servers.com-discreterate-public] url = "https://discreterate.com/mcp/v1"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-discreterate-public": {
"type": "remote",
"url": "https://discreterate.com/mcp/v1",
"enabled": true
}
}
} openclaw mcp add com-discreterate-public --url 'https://discreterate.com/mcp/v1' --transport streamable-http
mcp_servers:
com-discreterate-public:
url: "https://discreterate.com/mcp/v1" {
"McpServers": {
"com-discreterate-public": {
"Transport": "http",
"Url": "https://discreterate.com/mcp/v1"
}
}
} assistant mcp add com-discreterate-public -t streamable-http -u 'https://discreterate.com/mcp/v1'
{
"mcpServers": {
"com-discreterate-public": {
"type": "http",
"url": "https://discreterate.com/mcp/v1"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://discreterate.com/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=discreterate.com | CN=YE2,O=Let's Encrypt,C=US | 28 Jul 2026 | 26 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6f2ca5732d1bcdacbbafc660d214eec5971 |
| SANs: discreterate.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of discreterate.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| discreterate.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://discreterate.com/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://discreterate.com/mcp/v1 | HTTPS enforced | 301 | https://discreterate.com/mcp/v1 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe_demo ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| demo | string | yes | Which DRS demo to act on. See list_drs_demos for the catalog. |
No output schema declared.
No examples provided.
explain_des_vs_drs_event_complexity ~94
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
explain_discrete_rate_simulation ~98
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
explain_paradigm_integration ~83
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
explain_three_primitives ~67
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_drs_demos ~75
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_chocolate_processing ~127
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_fast_slow_drain ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| simulation_minutes | integer | – | Total simulation horizon in minutes. Default 100. Range 10-1000. |
No output schema declared.
No examples provided.
run_hamburger_duo ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| simulation_days | integer | – | Days to simulate. Default 7. Range 1-30. |
No output schema declared.
No examples provided.
run_showcase ~401
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.
| Name | Type | Req | Description |
|---|---|---|---|
| demo_id | string | yes | Which DRS demo to run live against the real engine. |
| knobs | object | – | 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… |
No output schema declared.
No examples provided.
run_sku_capacity ~135
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_tissue_line ~145
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_valdez_tanker ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| simulation_days | integer | – | Days to simulate. Default 30. Range 1-90. |
No output schema declared.
No examples provided.
run_vegetable_plant ~117
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the DiscreteRate MCP server?
DiscreteRate is an MCP server listed in the public MCP registry as com.discreterate/public. Run DRS demos (Fast-Slow Drain, Hamburger Duo, Valdez Tanker) and explore the paradigm. This page covers its hosted endpoint (https://discreterate.com/mcp/v1).
Is the DiscreteRate MCP server safe to use?
DiscreteRate scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DiscreteRate MCP server expose?
DiscreteRate exposes 14 tools: run_fast_slow_drain, run_hamburger_duo, run_valdez_tanker, run_vegetable_plant, run_chocolate_processing, and 9 more. Their descriptions and schemas cost roughly 1,791 tokens of context every time the server is loaded.
Does the DiscreteRate MCP server require authentication?
No. We connected to DiscreteRate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DiscreteRate MCP server still maintained?
DiscreteRate is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.