Remote MCP · Endpoint
AgentPay — Pay-per-call AI Microservices MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://agentpay.help/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- help.agentpay/agentpay
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 34 tools
- Uptime, last 30 days
- 92.9% from 14 checks
- Described by its publisher as
- 34 pay-per-call AI and data tools over x402; USDC on Base; no API keys.
- Website
- https://agentpay.help/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Handshake completed | 154 ms |
| 10 days ago | Handshake completed | 409 ms |
| 11 days ago | Handshake completed | 137 ms |
| 12 days ago | Handshake completed | 139 ms |
| 14 days ago | Handshake completed | 102 ms |
| 14 days ago | Handshake completed | 138 ms |
| 15 days ago | Handshake completed | 120 ms |
| 17 days ago | Handshake completed | 233 ms |
| 19 days ago | Handshake completed | 130 ms |
| 21 days ago | Handshake completed | 148 ms |
| 24 days ago | Handshake completed | 156 ms |
| 26 days ago | Handshake completed | 106 ms |
| 28 days ago | Handshake completed | 131 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 25.
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 AgentPay — Pay-per-call AI Microservices and makes no claim about it beyond what these checks measured.