Remote MCP · Endpoint
io.github.Kali123411/k402 MCP server
No. io.github.Kali123411/k402 answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://x402-compute.68cxgfyr0.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Kali123411/k402
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.85 s
- Tools exposed
- 36 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Agent-payable APIs on Kaspa: LLMs, chain data, covenants, zk proofs — pay per call, no API key
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 1.85 s |
| 2 days ago | Handshake completed | 252 ms |
| 4 days ago | Handshake completed | 231 ms |
| 5 days ago | Handshake completed | 190 ms |
| 7 days ago | Handshake completed | 259 ms |
| 8 days ago | Handshake completed | 290 ms |
| 9 days ago | Handshake completed | 155 ms |
| 12 days ago | Handshake completed | 354 ms |
| 13 days ago | Handshake completed | 310 ms |
| 15 days ago | Handshake completed | 213 ms |
| 17 days ago | Handshake completed | 213 ms |
| 18 days ago | Handshake completed | 234 ms |
| 19 days ago | Handshake completed | 198 ms |
| 20 days ago | Handshake completed | 196 ms |
| 20 days ago | Handshake completed | 176 ms |
| 21 days ago | Handshake completed | 192 ms |
| 23 days ago | Handshake completed | 220 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 io.github.Kali123411/k402 and makes no claim about it beyond what these checks measured.