Remote MCP · Endpoint

x402 Oracle MCP server

No. x402 Oracle answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://x402orcle.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.kwizzlesurp10-ctrl/x402orcle
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
57 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Paid x402 help: debug 402 errors, review MCP manifests, rewrite Bazaar listings. USDC on Base.
Listing
From the official MCP registry (active).
Recent checks of x402 Oracle
CheckedResultHandshake
13 minutes agoHandshake completed57 ms
9 days agoHandshake completed68 ms
9 days agoHandshake completed76 ms
11 days agoHandshake completed60 ms
12 days agoHandshake completed77 ms
13 days agoHandshake completed123 ms
14 days agoHandshake completed77 ms
15 days agoHandshake completed110 ms
16 days agoHandshake completed148 ms
19 days agoHandshake completed84 ms
21 days agoHandshake completed59 ms
24 days agoHandshake completed86 ms
26 days agoHandshake completed96 ms
28 days agoHandshake completed88 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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 x402 Oracle and makes no claim about it beyond what these checks measured.