Remote MCP · Endpoint
CoinGraph MCP server
No — it is up, but it requires credentials. CoinGraph answered 2 hours ago with an authentication challenge rather than a session.
Auth requiredLast checked 2 hours ago
Server URL
https://coingraph.ai/api/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- ai.coingraph/coingraph
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 22 tools
- Uptime, last 30 days
- 61.1% from 18 checks
- Described by its publisher as
- Pre-trade crypto intelligence: survival rating, order-book depth, unlocks and contract flags.
- Website
- https://coingraph.ai/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Credentials required | — |
| 1 day ago | Credentials required | — |
| 3 days ago | Credentials required | — |
| 3 days ago | Credentials required | — |
| 4 days ago | Credentials required | — |
| 5 days ago | Credentials required | — |
| 7 days ago | Credentials required | — |
| 10 days ago | Handshake completed | 287 ms |
| 12 days ago | Handshake completed | 280 ms |
| 14 days ago | Handshake completed | 287 ms |
| 17 days ago | Failed - the check failed for an unclassified reason | — |
| 19 days ago | Failed - the check failed for an unclassified reason | — |
| 21 days ago | Failed - the check failed for an unclassified reason | — |
| 23 days ago | Failed - the check failed for an unclassified reason | — |
| 25 days ago | Failed - the check failed for an unclassified reason | — |
| 26 days ago | Failed - the check failed for an unclassified reason | — |
| 28 days ago | Failed - the check failed for an unclassified reason | — |
| 29 days ago | Handshake completed | 96 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 22 responding of 29.
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 CoinGraph and makes no claim about it beyond what these checks measured.