Remote MCP · Endpoint
APEX on Arc MCP server
No. APEX on Arc answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://apexfaucet.xyz/api/mcp/arc
The last check completed an MCP handshake.
- Registry name
- xyz.apexfaucet/apex-arc
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 733 ms
- Tools exposed
- 69 tools
- Uptime, last 30 days
- 87.5% from 16 checks
- Described by its publisher as
- Arc for agents: token prices, rug checks (holders, dev pulls), launch exits, free USDC, paid APIs.
- Website
- https://apexfaucet.xyz/arc/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 733 ms |
| 2 days ago | Handshake completed | 1.17 s |
| 4 days ago | Handshake completed | 352 ms |
| 5 days ago | Handshake completed | 340 ms |
| 7 days ago | Handshake completed | 328 ms |
| 8 days ago | Handshake completed | 309 ms |
| 9 days ago | Failed - the request timed out | — |
| 12 days ago | Handshake completed | 218 ms |
| 13 days ago | Handshake completed | 373 ms |
| 15 days ago | Handshake completed | 347 ms |
| 17 days ago | Handshake completed | 327 ms |
| 18 days ago | Handshake completed | 337 ms |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Handshake completed | 339 ms |
| 20 days ago | Handshake completed | 387 ms |
| 21 days ago | Handshake completed | 329 ms |
The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 16.
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 on Arc and makes no claim about it beyond what these checks measured.