# Routescore MCP server

Read-only pre-sign evidence for onchain agents: route quality, MEV exposure, clear/caution verdict.

## Links
- Registry page: https://www.getdrio.com/mcp/io-routescore-mcp
- Repository: https://github.com/routescore/mcp
- Website: https://www.routescore.io/developers

## Install
- Command: `npx -y @routescore/mcp`
- Endpoint: https://www.routescore.io/api/mcp
- Auth: Auth required by registry metadata

## Setup notes
- Remote header: Authorization (required; secret)
- Package: Npm @routescore/mcp v0.3.5
- Environment variable: ROUTESCORE_API_KEY (required; secret)
- Environment variable: ROUTESCORE_API_URL
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://www.routescore.io/api/mcp
- Header: Authorization

## Tools
- check_swap (Check swap before signing (pre-sign evidence)) - 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 where observable, and a token registry read (recognized vs unverified), composed into a clear / caution / unsupported verdict with machine-readable reasons and caveats. Point-in-time decision support: it does not execute, route funds, sign, or promise an outcome — the agent still decides. Recognition is not safety, sellability, redemption, rights, liquidity, or investment-quality verification; unverified tokens, unknown order flow, and uncalibrated sequencer ordering downgrade the verdict rather than reading as safe. Relay the verdict, reasons, and caveats verbatim. Endpoint: https://www.routescore.io/api/mcp
- get_preflight_record (Retrieve pre-sign evidence 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 records belonging to its own account. The record embeds the evaluated check_swap response payload (including its evidence_bundle_id, before the additive record_id / record_output_hash linkage fields) plus a canonical-JSON SHA-256 integrity hash (record_id and recorded_at excluded) so the evidence can be re-verified offline, and includes the stored evidence bundle. Read-only evidence: record creation rejects known execution-material keys (calldata, transaction payloads, signing material) and drops identity-shaped labels from the actor context. Endpoint: https://www.routescore.io/api/mcp
- record_execution (Record immutable execution evidence) - 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. Pro tier, owner-scoped, and bounded by the MCP transport byte limit. This tool never accepts calldata, signing material, routes funds, executes a transaction, applies reviewer overrides, or exposes another tenant. Invalid rows are recorded only as redacted rejection reasons and are never echoed. Endpoint: https://www.routescore.io/api/mcp
- review_execution (Review stored execution evidence) - 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, unavailable-evidence register, caveats, and canonical hash. Read-only retrospective decision support only: it does not query arbitrary public transactions, accept reviewer overrides, certify best execution or compliance, give advice, or expose admin actions. Endpoint: https://www.routescore.io/api/mcp
- review_public_transaction (Review public Ethereum 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 owner-scoped stored execution_record.v1 and never exposes tenant, reviewer, override, or administrative fields. Returns the deterministic tenant-free public_transaction_review.v1 coverage register, conclusions, explicit gap register, source provenance, caveats, and canonical hash. Receipt, block, index, and gas facts are measured; gas cost and point-in-time confirmation depth are calculated. Venue is unavailable in this endpoint until a server-owned verified registry adapter exists. Route, amounts, protocol fee, arrival price, feasible-route benchmark, dropped status, and historical reorg remain unavailable unless the public contract can support them. Read-only retrospective decision support only; it does not certify best execution or compliance and does not give advice. Endpoint: https://www.routescore.io/api/mcp
- whoami (Verify API key & tier) - Confirm the configured API key works and report which plan tier it carries. Returns the owning account email and tier. Endpoint: https://www.routescore.io/api/mcp
- get_detector_manifest (Get MEV-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. Endpoint: https://www.routescore.io/api/mcp
- quote_mev_cover (Quote: MEV-sandwich premium (modeled)) - 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 premium-acceptance offer. Endpoint: https://www.routescore.io/api/mcp
- quote_bridge_refund (Quote: bridge-failure premium (modeled)) - 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. Endpoint: https://www.routescore.io/api/mcp
- quote_lrt_slashing (Quote: LRT-slashing premium (modeled)) - 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. Endpoint: https://www.routescore.io/api/mcp
- simulate_scenario (Simulate premium-vs-loss scenario (modeled)) - 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. Endpoint: https://www.routescore.io/api/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.routescore
- Version: 0.3.5
- Runtime: Npm
- Transports: STDIO, HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jul 19, 2026
- Source: https://registry.modelcontextprotocol.io