Remote MCP · Endpoint
MCP x402 - Evidence-Backed Web Verification MCP server
No. MCP x402 - Evidence-Backed Web Verification answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp-x402-production.up.railway.app/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Diogoup26/mcp-x402
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 127 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Evidence-backed pre-purchase checks for offer terms, seller trust and policy compliance.
- Repository
- https://github.com/Diogoup26/mcp-x402
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 127 ms |
| 1 day ago | Handshake completed | 115 ms |
| 2 days ago | Handshake completed | 117 ms |
| 3 days ago | Handshake completed | 107 ms |
| 4 days ago | Handshake completed | 130 ms |
| 5 days ago | Handshake completed | 145 ms |
| 6 days ago | Handshake completed | 120 ms |
| 9 days ago | Handshake completed | 119 ms |
| 11 days ago | Handshake completed | 107 ms |
| 14 days ago | Handshake completed | 121 ms |
| 16 days ago | Handshake completed | 126 ms |
| 18 days ago | Handshake completed | 130 ms |
| 20 days ago | Handshake completed | 113 ms |
| 22 days ago | Handshake completed | 115 ms |
| 24 days ago | Handshake completed | 118 ms |
| 26 days ago | Handshake completed | 108 ms |
| 27 days ago | Handshake completed | 115 ms |
| 29 days ago | Handshake completed | 110 ms |
The last 18 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 MCP x402 - Evidence-Backed Web Verification and makes no claim about it beyond what these checks measured.