Remote MCP · Endpoint

Run Budget Guard MCP server

No. Run Budget Guard answered an MCP handshake 14 minutes ago.

UpLast checked 14 minutes ago

Server URL

https://budget.cloudforbots.com/mcp

The last check completed an MCP handshake.

Registry name
com.botrecipe/budget
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
214 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Hard dollar, token, call and time caps shared by every sub-agent in one agent run.
Listing
From the official MCP registry (active).
Recent checks of Run Budget Guard
CheckedResultHandshake
14 minutes agoHandshake completed214 ms
9 days agoHandshake completed217 ms
9 days agoHandshake completed190 ms
11 days agoHandshake completed220 ms
12 days agoHandshake completed230 ms
13 days agoHandshake completed278 ms
14 days agoHandshake completed179 ms
14 days agoHandshake completed226 ms
16 days agoHandshake completed609 ms
19 days agoHandshake completed205 ms
21 days agoHandshake completed165 ms
24 days agoHandshake completed169 ms
26 days agoHandshake completed121 ms
28 days agoHandshake completed197 ms

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

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