Skip to main content
MCP server CX Codex

Routescore — Claude Code MCP server: pre-sign swap checks

A read-only MCP server that returns a route-quality, MEV-exposure and token-recognition verdict before a swap gets signed.

Install into Claude Code · Platform CLI All methods and platforms ↓
claude mcp add --env ROUTESCORE_API_KEY=<ROUTESCORE_API_KEY> --env ROUTESCORE_API_URL=<ROUTESCORE_API_URL> --transport stdio routescore -- npx -y @routescore/mcp
Open on GitHub

What Routescore does

An agent calls check_swap before signing. Back comes a clear / caution / unsupported verdict with caveats: modeled route quality, a slippage and price-impact band, modeled MEV exposure where it can be observed, and a token-registry read showing whether the token is recognized or unverified. Ethereum (1) and Robinhood Chain (4663) are supported. Registry recognition is not a statement about safety, sellability, rights, redemption or liquidity.

The server keeps no local copy of requests or responses — it is a stateless wrapper over the Routescore public API. Every keyed call tries to persist a hash-verifiable evidence record and returns record_id, evidence_bundle_id and record_output_hash. When the record store is down those fields come back null alongside a record_persistence_failed caveat. get_preflight_record fetches a stored record by record_id; it is scoped to the key's account and carries a canonical-JSON SHA-256 hash so the evidence can be re-checked offline.

A key is mandatory. Without ROUTESCORE_API_KEY the server exits at startup. The value is only shape-checked — rs_live_ plus 64 lowercase hex characters — while real verification stays server-side; run whoami for that. Keys are free to mint under Account → Developer → API & MCP access and are shown once. check_swap is free: 100 checks a day on a free key, 1,000 on Pro, 10,000 on Power. The quote_* tools, simulate_scenario and retrieval of stored records sit on the Power tier.

What it helps with

  • check a swap before signing and get a verdict with caveats
  • estimate MEV exposure and the slippage band for a route
  • persist a hash-verifiable record of what was known before signing
  • fetch a preflight record by record_id and re-verify it offline
  • see whether a token is recognized in the registry before trading

Example prompts for the agent

  • Run check_swap on this swap and show me the verdict with its caveats
  • Fetch the preflight record for record_id and check its hash
  • Call whoami and tell me which plan tier the key is on

How to install Routescore

1Platform CLI

claude mcp add --env ROUTESCORE_API_KEY=<ROUTESCORE_API_KEY> --env ROUTESCORE_API_URL=<ROUTESCORE_API_URL> --transport stdio routescore -- npx -y @routescore/mcp

Replace <…> with your own values

2Platform CLI: remote server

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

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about Routescore

How do I install Routescore in Claude Code?

Run claude mcp add routescore --env ROUTESCORE_API_KEY=rs_live_... -- npx -y @routescore/mcp with your own key.

What does Routescore do?

It is a read-only MCP server for pre-sign swap checks: a verdict on route quality, MEV exposure and token recognition, plus a verifiable evidence record. It never signs transactions or moves funds.

Does the server need an API key?

Yes — it exits at startup without ROUTESCORE_API_KEY. Keys are free to mint under Account → Developer → API & MCP access.

Similar MCP servers

All MCP servers for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor