Skip to content
External endpointresponds

Routescore

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

Endpoint URL
https://www.routescore.io/api/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:09 AM UTC
Check
MCP initialize · 8s limit
Latency
1,392 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.routescore/mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
routescore
Version
0.4.0
Capability keys
tools
Tool names
check_swap, get_preflight_record, record_execution, review_execution, review_public_transaction, whoami, get_detector_manifest, quote_mev_cover, quote_bridge_refund, quote_lrt_slashing, simulate_scenario
Instructions excerpt

Routescore is a read-only pre-sign evidence layer for onchain agents — one element of the agentic execution stack, not the executor and not a guarantee. Primary tool: check_swap. Call it AFTER you have constructed a proposed swap and BEFORE you sign it or hand it to an executor. Given the notional, chain, and (optionally) the route and token, it returns a clear / caution / unsupported verdict with machine-readable reasons and caveats, and persists a hash-verifiable record of exactly what was known before signing. check_swap never signs, executes, routes funds, or custodies assets — the calling agent still decides whether to proceed. Relay the verdict, reasons, and caveats to the user or downstream executor verbatim: do not paraphrase away a caution or drop a caveat. Treat a verdict of "unsupported" as first-class evidence ("not evaluated"), not an error to retry around. Every check_swap call returns a record_id; use get_preflight_record to fetch that durable, offline-re-verifiab

Reported Aug 17, 2026, 05:09 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 171ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 620ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 199ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 1,392ms