Remote MCP · Endpoint

io.github.Carlos-VLab/routing-services-courier MCP server

No. io.github.Carlos-VLab/routing-services-courier answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://routing-courier-mcp-production.up.railway.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.Carlos-VLab/routing-services-courier
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
156 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Pay-per-call ($0.01 USDC) model-routing for AI coding agents: which LLM to call, cost vs. quality.
Listing
From the official MCP registry (active).
Recent checks of io.github.Carlos-VLab/routing-services-courier
CheckedResultHandshake
1 hour agoHandshake completed156 ms
2 days agoHandshake completed114 ms
4 days agoHandshake completed117 ms
5 days agoHandshake completed139 ms
7 days agoHandshake completed170 ms
8 days agoHandshake completed97 ms
9 days agoHandshake completed126 ms
12 days agoHandshake completed99 ms
13 days agoHandshake completed94 ms
15 days agoHandshake completed94 ms
16 days agoHandshake completed94 ms
18 days agoHandshake completed100 ms
19 days agoHandshake completed122 ms
20 days agoHandshake completed103 ms
20 days agoHandshake completed98 ms
21 days agoHandshake completed95 ms
22 days agoHandshake completed96 ms

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.Carlos-VLab/routing-services-courier and makes no claim about it beyond what these checks measured.