Remote MCP · Endpoint
mcp-x402 — MCP server for agents with autonomous USDC/RLUSD payments MCP server
No. mcp-x402 — MCP server for agents with autonomous USDC/RLUSD payments answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp-x402.onrender.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Timwal78/mcp-x402
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 123 ms
- Tools exposed
- 12 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- 85+ pay-per-call MCP tools: trading, federal grants/contracts, SEC, FTD. x402 USDC/RLUSD. No keys.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 123 ms |
| 10 hours ago | Handshake completed | 167 ms |
| 1 day ago | Handshake completed | 135 ms |
| 2 days ago | Handshake completed | 132 ms |
| 4 days ago | Handshake completed | 129 ms |
| 4 days ago | Handshake completed | 121 ms |
| 5 days ago | Handshake completed | 139 ms |
| 6 days ago | Handshake completed | 157 ms |
| 8 days ago | Handshake completed | 292 ms |
| 11 days ago | Handshake completed | 143 ms |
| 13 days ago | Handshake completed | 284 ms |
| 16 days ago | Handshake completed | 310 ms |
| 18 days ago | Handshake completed | 316 ms |
| 20 days ago | Handshake completed | 139 ms |
| 22 days ago | Handshake completed | 328 ms |
| 24 days ago | Handshake completed | 150 ms |
| 26 days ago | Handshake completed | 163 ms |
| 27 days ago | Handshake completed | 301 ms |
| 29 days ago | Handshake completed | 282 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 mcp-x402 — MCP server for agents with autonomous USDC/RLUSD payments and makes no claim about it beyond what these checks measured.