Remote MCP · Endpoint
dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema MCP server
No. dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://ghost-identity.ghost-agent-os.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 321 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 94.1% from 17 checks
- Described by its publisher as
- Web search for agents, one x402 payment: real results, provider failover, signed receipt. $0.01.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 321 ms |
| 2 days ago | Handshake completed | 257 ms |
| 4 days ago | Handshake completed | 347 ms |
| 5 days ago | Handshake completed | 559 ms |
| 7 days ago | Handshake completed | 349 ms |
| 8 days ago | Handshake completed | 356 ms |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 12 days ago | Handshake completed | 426 ms |
| 13 days ago | Handshake completed | 554 ms |
| 15 days ago | Handshake completed | 232 ms |
| 16 days ago | Handshake completed | 398 ms |
| 18 days ago | Handshake completed | 427 ms |
| 19 days ago | Handshake completed | 232 ms |
| 20 days ago | Handshake completed | 512 ms |
| 20 days ago | Handshake completed | 536 ms |
| 21 days ago | Handshake completed | 350 ms |
| 22 days ago | Handshake completed | 633 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 17.
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 dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema and makes no claim about it beyond what these checks measured.