B-

discreterate.com

https://discreterate.com/mcp/v1
81/100 · MCP Trust Grade · checked 4h ago · MCP 2025-06-18
Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 9 tools · Other

run_fast_slow_drain

Run the Fast-Slow Drain (FSD) demo — Damiron-Nastasi 2008 oscillating tank. The canonical DRS-vs-DES event-count demonstration. Returns engine output

run_hamburger_duo

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 e

run_valdez_tanker

Run the Valdez Tanker (VALD) demo — Koelling-Remy 1983 Alaska Pipeline model, the paradigm-integration motivator. Crude flows continuously into the Va

list_drs_demos

List the three canonical DRS demos (Fast-Slow Drain · Hamburger Duo · Valdez Tanker). Each demo is documented in academic literature and reproducible

describe_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_discrete_rate_simulation

Return a textbook-tier explainer of Discrete Rate Simulation: how it differs from DES and CT, the three primitives (Constraint / Buffer / Interrupt),

explain_three_primitives

Return a focused write-up of the three DRS modeling primitives: Constraint (rate-limiter), Buffer (accumulated state), Interrupt (stoppage). Use this

explain_paradigm_integration

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) primitiv

explain_des_vs_drs_event_complexity

Return a focused write-up of the event-count complexity differences between DES and DRS, with the worked Fast-Slow Drain numbers (Continuous ~thousand

Spec conformance20%100
Security (OWASP MCP)30%100
Reliability / performance20%70
Tool hygiene15%46
Transparency / provenance15%70

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.
Grade another server

We re-grade discreterate.com on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — discreterate.com grade B-
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade B- · wmcp.sh
[![MCP Trust Grade B-](https://wmcp.sh/mcp/grade/discreterate.com/badge.svg)](https://wmcp.sh/mcp/grade/discreterate.com)
<a href="https://wmcp.sh/mcp/grade/discreterate.com"><img src="https://wmcp.sh/mcp/grade/discreterate.com/badge.svg" alt="MCP Trust Grade B- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.