Remote MCP · Endpoint
cp0x public data MCP server
No. cp0x public data answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.cp0x.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.cp0x/public-data
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 289 ms
- Tools exposed
- 12 tools
- Uptime, last 30 days
- 100% from 5 checks
- Described by its publisher as
- Read-only cp0x data: referral deals and races, DeFi geo-restrictions, and x402 catalogs.
- Repository
- https://github.com/cp0x-org/cp0x-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 289 ms |
| 7 hours ago | Handshake completed | 273 ms |
| 2 days ago | Handshake completed | 277 ms |
| 4 days ago | Handshake completed | 283 ms |
| 6 days ago | Handshake completed | 276 ms |
The last 5 checks. Full history is kept for 30 days; the all-time counter stands at 5 responding of 5.
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 cp0x public data and makes no claim about it beyond what these checks measured.