Remote MCP · Endpoint
APEX web reader MCP server
No. APEX web reader answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://apexfaucet.xyz/api/mcp/web
The last check completed an MCP handshake.
- Registry name
- xyz.apexfaucet/apex-web
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 451 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 94.4% from 18 checks
- Described by its publisher as
- A real browser for your agent: a page to clean text for $0.009, a 25-page site for $0.14. x402.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 451 ms |
| 1 day ago | Handshake completed | 402 ms |
| 2 days ago | Handshake completed | 175 ms |
| 3 days ago | Handshake completed | 455 ms |
| 4 days ago | Handshake completed | 342 ms |
| 5 days ago | Handshake completed | 218 ms |
| 6 days ago | Handshake completed | 422 ms |
| 9 days ago | Handshake completed | 430 ms |
| 11 days ago | Handshake completed | 581 ms |
| 14 days ago | Handshake completed | 784 ms |
| 16 days ago | Failed - the request timed out | — |
| 18 days ago | Handshake completed | 343 ms |
| 20 days ago | Handshake completed | 3.47 s |
| 22 days ago | Handshake completed | 371 ms |
| 24 days ago | Handshake completed | 331 ms |
| 26 days ago | Handshake completed | 332 ms |
| 28 days ago | Handshake completed | 335 ms |
| 29 days ago | Handshake completed | 406 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 28.
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 web reader and makes no claim about it beyond what these checks measured.