Remote MCP · Endpoint

orbit x402 Picks MCP server

No. orbit x402 Picks answered an MCP handshake 17 hours ago.

UpLast checked 17 hours ago

Server URL

https://x402-picks.orbit-builder.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.orbit-builder.x402-picks/x402-picks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
300 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Which x402 endpoint to call: ranked by relevance, payers, recency, price. $0.005/call via x402.
Listing
From the official MCP registry (active).
Recent checks of orbit x402 Picks
CheckedResultHandshake
17 hours agoHandshake completed300 ms
11 days agoHandshake completed196 ms
12 days agoHandshake completed465 ms
12 days agoHandshake completed229 ms
14 days agoHandshake completed205 ms
15 days agoHandshake completed336 ms
16 days agoHandshake completed203 ms
17 days agoHandshake completed204 ms
18 days agoHandshake completed402 ms
20 days agoHandshake completed990 ms
22 days agoHandshake completed210 ms
25 days agoHandshake completed304 ms

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

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