Remote MCP · Endpoint

io.github.NonSynthetic/apex-edge MCP server

No. io.github.NonSynthetic/apex-edge 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
io.github.NonSynthetic/apex-edge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
184 ms
Tools exposed
14 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
x402 machine-payable utility edge: 19 curated MCP tools + ~450-SKU REST catalog, priced in USDC
Listing
From the official MCP registry (active).
Recent checks of io.github.NonSynthetic/apex-edge
CheckedResultHandshake
3 hours agoHandshake completed184 ms
4 days agoHandshake completed313 ms
7 days agoHandshake completed181 ms

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

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 io.github.NonSynthetic/apex-edge and makes no claim about it beyond what these checks measured.