Skip to content
Routescore logo

Routescore MCP server

Which servers in the official MCP registry are Routescore's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Routescore

Whose server it is
  • Registry nameio.routescore/mcpverified in the MCP registry

The registry name sits under routescore.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools11
  • Server calls itselfroutescore
  • Server version0.4.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 145 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Estimate modeled route cost before approving a transaction; Compare alternative routes at the same trade size.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "Estimate modeled route cost before approving a transaction", the likely first call is check_swap.
  • For "Compare alternative routes at the same trade size", the likely first call is check_swap.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it2 of 2 use cases
  • Use22 npm downloads a week
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer232 ms
  • Space in an agent's context≈ 2,734 tokensthe definitions of all its tools (11), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results11 of 11 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Estimate modeled route cost before approving a transaction
  • can do · Compare alternative routes at the same trade size
  • not sure · Export and save route decisions as shareable records

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers11 tools · read 2026-10-26
  • check_swap

    CALL THIS BEFORE SIGNING AN ONCHAIN SWAP. Read-only pre-sign evidence check: given notional, chain, and an optional route and token, it returns a modeled route-quality grade, price-impact / slippage band, modeled MEV/execution exposure…

  • get_preflight_record

    Retrieve the durable evidence record a prior check_swap call persisted — the "record" leg of plan → preflight → execute → record. Fetch one record by the record_id that check_swap returned. Owner-scoped: the configured key only ever sees…

  • record_execution

    Persist 1-100 already-built execution_record.v1 documents as immutable, personal-account post-trade evidence. Requires a stable idempotency_key; an exact replay returns the original result and reuse with different content fails closed…

  • review_execution

    Review one stored execution_record.v1 by record_id. Authenticated and personal-account owner-scoped: another account’s id is indistinguishable from a missing id. Returns the deterministic review_execution.v1 evidence coverage, exceptions…

  • review_public_transaction

    DEV-ONLY CONTRACT DISCOVERY; DISABLED AGAINST PRODUCTION. On an explicitly enabled non-production server, review one arbitrary public Ethereum transaction by transaction hash. This is separate from review_execution: it does not read an…

  • whoami

    Confirm the configured API key works and report which plan tier it carries. Returns the owning account email and tier.

  • get_detector_manifest

    Fetch the latest public MEV-detector run manifest: the detector version hash and the eligible pool/token universe it was committed to. Use to verify what the detector covers.

  • quote_mev_cover

    Modeled premium estimate for MEV-sandwich exposure on a swap. Returns a modeled premium (bps + USD), expected/CVaR loss, and conditions. Point-in-time decision support before routing a trade — not a live cover, insurance, or…

  • quote_bridge_refund

    Modeled premium estimate for cross-chain bridge execution failure against a modeled SLA expectation. Returns a modeled premium and conditions — not a live cover, refund, or premium-acceptance offer.

  • quote_lrt_slashing

    Modeled premium estimate for slashing risk on a liquid-restaking-token (LRT) position given its AVS exposure. Returns a modeled premium and slashing bounds — not a live cover offer.

  • simulate_scenario

    Run a what-if Monte Carlo: model expected premium vs expected refund/loss over a horizon, given assumptions about sandwich frequency, average loss, and deductible. Returns a narrative + distribution.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "routescore": {
      "type": "http",
      "url": "https://www.routescore.io/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http routescore https://www.routescore.io/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://www.routescore.io/api/mcp as a custom connector in the settings.

Also shipped through: npm

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.