Skip to content

DiscreteRate MCP server

com.discreterate/publicdiscreterate.comstreamable-httpv1.0.0Scanned

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

14 tools: 8 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 8 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 8 findings

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the DiscreteRate MCP server can do

The DiscreteRate MCP server is published by discreterate.com, a domain the MCP Registry verified. It has 14 tools. It can create or change data (8 tools: run_fast_slow_drain, run_hamburger_duo, run_valdez_tanker, run_vegetable_plant and 4 more), but cannot delete data. 6 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 8 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Changes things 8Claude Code: ask
  • run_chocolate_processingRun the Chocolate Processing (CHOC) demo — Plant Builder's joint DES↔DRS bridge.1 finding

    Why it is in this group

    • The name "run_chocolate_processing" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "run_chocolate_processing" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_chocolate_processing" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run Chocolate Processing (Plant Builder DES↔DRS bridge)
  • run_fast_slow_drainRun the Fast-Slow Drain (FSD) demo — Damiron-Nastasi 2008 oscillating tank.1 finding

    Why it is in this group

    • The name "run_fast_slow_drain" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "run_fast_slow_drain" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_fast_slow_drain" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run Fast-Slow Drain (Damiron-Nastasi 2008)
  • run_hamburger_duoRun 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 numb…1 finding

    Why it is in this group

    • The name "run_hamburger_duo" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "run_hamburger_duo" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_hamburger_duo" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run Hamburger Duo (Siprelle, DES + DRS side-by-side)
  • run_showcaseLIVE EXPERIMENT — run a DRS demo against the real engine with parameters you choose, and get its verbatim run envelope (metadata, execution stats, metrics, details).1 finding

    Why it is in this group

    • The name "run_showcase" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "run_showcase" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "run_showcase" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run a DRS demo live (your parameters)
  • run_sku_capacityRun the Bottling Line / SKU-capacity (SKU) demo — a sim-foundation parameter-set example.1 finding

    Why it is in this group

    • The name "run_sku_capacity" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "run_sku_capacity" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_sku_capacity" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run Bottling Line SKU capacity
  • run_tissue_lineRun the Tissue Line (TIS) demo — a sim-foundation parameter-set example.1 finding

    Why it is in this group

    • The name "run_tissue_line" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "run_tissue_line" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_tissue_line" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run Tissue Line strategic decision
  • run_valdez_tankerRun the Valdez Tanker (VALD) demo — Koelling-Remy 1983 Alaska Pipeline model, the paradigm-integration motivator.1 finding

    Why it is in this group

    • The name "run_valdez_tanker" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "run_valdez_tanker" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_valdez_tanker" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run Valdez Tanker (Koelling-Remy 1983)
  • run_vegetable_plantRun the Vegetable Plant (VEG) demo — a Plant Builder distribution-control model.1 finding

    Why it is in this group

    • The name "run_vegetable_plant" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "run_vegetable_plant" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_vegetable_plant" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run Vegetable Plant (Plant Builder distribution control)
Only reads 6Show 6 read-only tools
  • describe_demoFull per-demo write-up: history, what it teaches, what to expect from the run_* output.No findings

    Why it is in this group

    • The name "describe_demo" says "describe": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Describe one DRS demo
  • explain_des_vs_drs_event_complexityReturn 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…No findings

    Why it is in this group

    • The name "explain_des_vs_drs_event_complexity" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: DES vs DRS event-count primer
  • explain_discrete_rate_simulationReturn 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 /…No findings

    Why it is in this group

    • The name "explain_discrete_rate_simulation" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: DRS paradigm primer
  • explain_paradigm_integrationReturn 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.No findings

    Why it is in this group

    • The name "explain_paradigm_integration" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: F2I / I2F integration primer
  • explain_three_primitivesReturn a focused write-up of the three DRS modeling primitives: Constraint (rate-limiter), Buffer (accumulated state), Interrupt (stoppage).No findings

    Why it is in this group

    • The name "explain_three_primitives" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Three primitives primer
  • list_drs_demosList the seven DRS demos (Fast-Slow Drain · Hamburger Duo · Valdez Tanker · Vegetable Plant · Chocolate Processing · Bottling Line SKU capacity · Tissue Line).No findings

    Why it is in this group

    • The name "list_drs_demos" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List DRS canonical demos

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:37 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://discreterate.com/mcp/v1: tools/list returned 14 tools to an anonymous client, including run_fast_slow_drain (write), run_hamburger_duo (write), run_valdez_tanker (write), run_vegetable_plant (write), run_chocolate_processing (write) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

8 warn
  • The server marks "run_fast_slow_drain" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_fast_slow_drain" says "run": a word for a change.

    What this check looks for
  • The server marks "run_hamburger_duo" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_hamburger_duo" says "run": a word for a change.

    What this check looks for
  • The server marks "run_valdez_tanker" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_valdez_tanker" says "run": a word for a change.

    What this check looks for
  • The server marks "run_vegetable_plant" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_vegetable_plant" says "run": a word for a change.

    What this check looks for
  • The server marks "run_chocolate_processing" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_chocolate_processing" says "run": a word for a change.

    What this check looks for
  • The server marks "run_sku_capacity" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_sku_capacity" says "run": a word for a change.

    What this check looks for
Show 2 more findings
  • The server marks "run_tissue_line" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_tissue_line" says "run": a word for a change.

    What this check looks for
  • The server marks "run_showcase" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "run_showcase" says "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools14 changed.~14 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http public https://discreterate.com/mcp/v1
claude mcp add --transport http public https://discreterate.com/mcp/v1

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__public__list_drs_demos",
      "mcp__public__describe_demo",
      "mcp__public__explain_discrete_rate_simulation",
      "mcp__public__explain_three_primitives",
      "mcp__public__explain_paradigm_integration",
      "mcp__public__explain_des_vs_drs_event_complexity"
    ],
    "ask": [
      "mcp__public__run_fast_slow_drain",
      "mcp__public__run_hamburger_duo",
      "mcp__public__run_valdez_tanker",
      "mcp__public__run_vegetable_plant",
      "mcp__public__run_chocolate_processing",
      "mcp__public__run_sku_capacity",
      "mcp__public__run_tissue_line",
      "mcp__public__run_showcase"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as public. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.discreterate/public/verify?hash=6eb340ec79c8634a59d105f8585da38d281ba477ccaa631a099c045b64c6f906" | jq -e '.changed == false'

Pinned hash 6eb340ec79c8, from Nov 10, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.discreterate/public/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.discreterate/public
[![Anlyon Radar](https://radar.anlyon.com/badge/com.discreterate/public.svg)](https://radar.anlyon.com/servers/com.discreterate/public)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:54 UTC.

DiscreteRate MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the DiscreteRate MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 8 of which can change, send or delete something, and 8 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the DiscreteRate MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the DiscreteRate MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the DiscreteRate MCP server have?

14 tools: 8 write, 6 read. run_fast_slow_drain, run_hamburger_duo, run_valdez_tanker, run_vegetable_plant, run_chocolate_processing, run_sku_capacity, run_tissue_line, run_showcase and 6 more.

Does the DiscreteRate MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the DiscreteRate MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the DiscreteRate MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.