Remote MCP · Endpoint

Apex Edge — x402-paid machine services MCP server

No. Apex Edge — x402-paid machine services answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://api.nonsynthetic.net/mcp

The last check completed an MCP handshake.

Registry name
net.nonsynthetic/apex-edge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
320 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
x402-paid MCP tools & data APIs for agents — USDC on Base + Solana
Listing
From the official MCP registry (active).
Recent checks of Apex Edge — x402-paid machine services
CheckedResultHandshake
3 hours agoHandshake completed320 ms
3 days agoHandshake completed291 ms
13 days agoHandshake completed223 ms
14 days agoHandshake completed104 ms
15 days agoHandshake completed360 ms
16 days agoHandshake completed170 ms
18 days agoHandshake completed64 ms
18 days agoHandshake completed177 ms
19 days agoHandshake completed52 ms
21 days agoHandshake completed491 ms
22 days agoHandshake completed166 ms
25 days agoHandshake completed65 ms
27 days agoHandshake completed130 ms

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

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 Apex Edge — x402-paid machine services and makes no claim about it beyond what these checks measured.