Remote MCP · Endpoint

Agent Budget Router MCP server

No. Agent Budget Router answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://agent-budget-router-v7.movt1677.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.kasp3965-bit/agent-budget-router
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
435 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Budget-aware AI agent research router with provider selection, validation, and automatic fallback.
Listing
From the official MCP registry (active).
Recent checks of Agent Budget Router
CheckedResultHandshake
3 hours agoHandshake completed435 ms
9 days agoHandshake completed583 ms
10 days agoHandshake completed624 ms
11 days agoHandshake completed336 ms
12 days agoHandshake completed480 ms
14 days agoHandshake completed285 ms
14 days agoHandshake completed288 ms
15 days agoHandshake completed513 ms
17 days agoHandshake completed591 ms
19 days agoHandshake completed303 ms
21 days agoHandshake completed476 ms
24 days agoHandshake completed227 ms
26 days agoHandshake completed248 ms
28 days agoHandshake completed496 ms

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

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 Agent Budget Router and makes no claim about it beyond what these checks measured.