Remote MCP · Endpoint
Caper Wiki MCP server
No. Caper Wiki answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://caper.network/api/mcp
The last check completed an MCP handshake.
- Registry name
- network.caper/caper-wiki
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 248 ms
- Tools exposed
- 17 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Read Caper's wiki and DAO on-chain data; launch a DAO, trade, and propose on Radix testnet.
- Website
- https://caper.network/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 248 ms |
| 1 day ago | Handshake completed | 222 ms |
| 2 days ago | Handshake completed | 682 ms |
| 3 days ago | Handshake completed | 207 ms |
| 4 days ago | Handshake completed | 219 ms |
| 5 days ago | Handshake completed | 195 ms |
| 6 days ago | Handshake completed | 2.63 s |
| 8 days ago | Handshake completed | 219 ms |
| 11 days ago | Handshake completed | 236 ms |
| 13 days ago | Handshake completed | 232 ms |
| 16 days ago | Handshake completed | 246 ms |
| 18 days ago | Handshake completed | 164 ms |
| 20 days ago | Handshake completed | 109 ms |
| 22 days ago | Handshake completed | 80 ms |
| 24 days ago | Handshake completed | 106 ms |
| 26 days ago | Handshake completed | 84 ms |
| 27 days ago | Handshake completed | 109 ms |
| 29 days ago | Handshake completed | 93 ms |
| 29 days ago | Handshake completed | 1.74 s |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Caper Wiki and makes no claim about it beyond what these checks measured.