Remote MCP · Endpoint

Routescore MCP server

No. Routescore answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.routescore.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.routescore/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
157 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only pre-sign evidence for onchain agents: route quality, MEV exposure, clear/caution verdict.
Website
https://www.routescore.io/developers
Repository
https://github.com/routescore/mcp
Listing
From the official MCP registry (active).
Recent checks of Routescore
CheckedResultHandshake
1 hour agoHandshake completed157 ms
9 days agoHandshake completed130 ms
10 days agoHandshake completed156 ms
11 days agoHandshake completed144 ms
12 days agoHandshake completed158 ms
14 days agoHandshake completed174 ms
14 days agoHandshake completed150 ms
15 days agoHandshake completed332 ms
17 days agoHandshake completed288 ms
19 days agoHandshake completed230 ms
21 days agoHandshake completed129 ms
24 days agoHandshake completed2.57 s
26 days agoHandshake completed176 ms
28 days agoHandshake completed151 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Routescore and makes no claim about it beyond what these checks measured.