Remote MCP · Endpoint
xProof MCP server
No. xProof answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://xproof.app/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.jasonxkensei/xproof
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 263 ms
- Tools exposed
- 13 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
- Repository
- https://github.com/jasonxkensei/xProof
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 263 ms |
| 2 days ago | Handshake completed | 266 ms |
| 4 days ago | Handshake completed | 339 ms |
| 5 days ago | Handshake completed | 184 ms |
| 7 days ago | Handshake completed | 237 ms |
| 8 days ago | Handshake completed | 183 ms |
| 9 days ago | Handshake completed | 240 ms |
| 12 days ago | Handshake completed | 230 ms |
| 13 days ago | Handshake completed | 224 ms |
| 15 days ago | Handshake completed | 240 ms |
| 17 days ago | Handshake completed | 234 ms |
| 18 days ago | Handshake completed | 256 ms |
| 19 days ago | Handshake completed | 248 ms |
| 20 days ago | Handshake completed | 264 ms |
| 20 days ago | Handshake completed | 242 ms |
| 21 days ago | Handshake completed | 190 ms |
| 23 days ago | Handshake completed | 270 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 xProof and makes no claim about it beyond what these checks measured.