Remote MCP · Endpoint
ai.mcpanalytics/analytics MCP server
Yes, as of 7 hours ago: the server returned an HTTP error.
DownLast checked 7 hours ago
Server URL
https://api.mcpanalytics.ai/mcp/api-key
The last check failed: the server returned an HTTP error.
- Registry name
- ai.mcpanalytics/analytics
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 28 tools
- Uptime, last 30 days
- 94.1% from 17 checks
- Described by its publisher as
- The statistical analyst in your AI chat — validated, citable, re-runnable analysis of your data.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 7 hours ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Handshake completed | 697 ms |
| 4 days ago | Handshake completed | 249 ms |
| 5 days ago | Handshake completed | 259 ms |
| 7 days ago | Handshake completed | 282 ms |
| 8 days ago | Handshake completed | 282 ms |
| 9 days ago | Handshake completed | 244 ms |
| 12 days ago | Handshake completed | 291 ms |
| 13 days ago | Handshake completed | 270 ms |
| 15 days ago | Handshake completed | 261 ms |
| 16 days ago | Handshake completed | 277 ms |
| 17 days ago | Handshake completed | 287 ms |
| 19 days ago | Handshake completed | 292 ms |
| 19 days ago | Handshake completed | 276 ms |
| 20 days ago | Handshake completed | 266 ms |
| 21 days ago | Handshake completed | 262 ms |
| 23 days ago | Handshake completed | 421 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 ai.mcpanalytics/analytics and makes no claim about it beyond what these checks measured.