Remote MCP · Endpoint
spendctl MCP server
No. spendctl answered an MCP handshake 37 minutes ago.
UpLast checked 37 minutes ago
Server URL
https://mcp.spendctl.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.spendctl/spendctl
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 372 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Spend policy for AI agents that pay (x402, MPP). Login-free sandbox, real sidecar, no real funds.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 37 minutes ago | Handshake completed | 372 ms |
| 4 days ago | Handshake completed | 321 ms |
| 7 days ago | Handshake completed | 209 ms |
| 16 days ago | Handshake completed | 271 ms |
| 16 days ago | Handshake completed | 238 ms |
| 18 days ago | Handshake completed | 227 ms |
| 19 days ago | Handshake completed | 258 ms |
| 20 days ago | Handshake completed | 260 ms |
| 21 days ago | Handshake completed | 376 ms |
| 22 days ago | Handshake completed | 267 ms |
| 23 days ago | Handshake completed | 488 ms |
| 26 days ago | Handshake completed | 363 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 spendctl and makes no claim about it beyond what these checks measured.