Remote MCP · Endpoint

APEX Faucet MCP server

No. APEX Faucet answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://apexfaucet.xyz/mcp

The last check completed an MCP handshake.

Registry name
xyz.apexfaucet/apex-x1
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
137 ms
Tools exposed
397 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Page extract, markdown, tx check, delivery score. Pay per call, x402.
Listing
From the official MCP registry (active).
Recent checks of APEX Faucet
CheckedResultHandshake
2 days agoHandshake completed137 ms
6 days agoHandshake completed399 ms
16 days agoHandshake completed415 ms
17 days agoHandshake completed573 ms
17 days agoHandshake completed345 ms
19 days agoHandshake completed330 ms
21 days agoHandshake completed227 ms
21 days agoHandshake completed362 ms
22 days agoHandshake completed147 ms
23 days agoHandshake completed342 ms
25 days agoHandshake completed288 ms
28 days agoHandshake completed364 ms
30 days agoHandshake completed4.44 s

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

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