Remote MCP · Endpoint
io.github.cdkbotmcp/cdk-mcp MCP server
No. io.github.cdkbotmcp/cdk-mcp answered an MCP handshake 2 days ago.
UpLast checked 2 days ago
Server URL
https://mcp.cdk.bot/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.cdkbotmcp/cdk-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 352 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Buy game keys, gift cards, and subscriptions via x402 USDC on Base. 8 MCP tools, no install.
- Website
- https://cdk.bot/
- Repository
- https://github.com/cdkbotmcp/cdk-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 days ago | Handshake completed | 352 ms |
| 2 days ago | Handshake completed | 378 ms |
| 3 days ago | Handshake completed | 240 ms |
| 5 days ago | Handshake completed | 210 ms |
| 6 days ago | Handshake completed | 218 ms |
| 7 days ago | Handshake completed | 225 ms |
| 8 days ago | Handshake completed | 334 ms |
| 9 days ago | Handshake completed | 206 ms |
| 11 days ago | Handshake completed | 253 ms |
| 13 days ago | Handshake completed | 323 ms |
| 16 days ago | Handshake completed | 213 ms |
| 18 days ago | Handshake completed | 337 ms |
| 20 days ago | Handshake completed | 211 ms |
| 22 days ago | Handshake completed | 406 ms |
| 24 days ago | Handshake completed | 269 ms |
| 26 days ago | Handshake completed | 232 ms |
| 28 days ago | Handshake completed | 323 ms |
| 30 days ago | Handshake completed | 218 ms |
| 31 days ago | Handshake completed | 412 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 io.github.cdkbotmcp/cdk-mcp and makes no claim about it beyond what these checks measured.