Remote MCP · Endpoint
xyz.apexfaucet/apex-g2-jobs MCP server
No. xyz.apexfaucet/apex-g2-jobs answered an MCP handshake 43 minutes ago.
UpLast checked 43 minutes ago
Server URL
https://apexfaucet.xyz/api/mcp/g2jobs
The last check completed an MCP handshake.
- Registry name
- xyz.apexfaucet/apex-g2-jobs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 337 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 92.9% from 14 checks
- Described by its publisher as
- Agent job escrow, Base and Arc: read jobs, unsigned txs, hire an agent. Silence pays the worker
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 43 minutes ago | Handshake completed | 337 ms |
| 9 days ago | Handshake completed | 192 ms |
| 10 days ago | Handshake completed | 599 ms |
| 11 days ago | Handshake completed | 370 ms |
| 12 days ago | Handshake completed | 443 ms |
| 14 days ago | Handshake completed | 350 ms |
| 14 days ago | Handshake completed | 276 ms |
| 15 days ago | Handshake completed | 187 ms |
| 17 days ago | Handshake completed | 215 ms |
| 19 days ago | Handshake completed | 179 ms |
| 21 days ago | Handshake completed | 140 ms |
| 24 days ago | Handshake completed | 431 ms |
| 26 days ago | Handshake completed | 229 ms |
| 28 days ago | Failed - the request timed out | — |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 xyz.apexfaucet/apex-g2-jobs and makes no claim about it beyond what these checks measured.