Remote MCP · Endpoint
Staats MCP server
No. Staats answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://api.staats.ai/functions/v1/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.MrViolets/staats
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 668 ms
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Cookieless web analytics your coding agent reads: traffic answers, deploy impact, what broke.
- Website
- https://www.staats.ai/
- Repository
- https://github.com/MrViolets/staats-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 668 ms |
| 2 days ago | Handshake completed | 521 ms |
| 4 days ago | Handshake completed | 515 ms |
| 5 days ago | Handshake completed | 478 ms |
| 7 days ago | Handshake completed | 560 ms |
| 8 days ago | Handshake completed | 654 ms |
| 9 days ago | Handshake completed | 594 ms |
| 12 days ago | Handshake completed | 544 ms |
| 13 days ago | Handshake completed | 524 ms |
| 15 days ago | Handshake completed | 472 ms |
| 17 days ago | Handshake completed | 508 ms |
| 18 days ago | Handshake completed | 652 ms |
| 19 days ago | Handshake completed | 488 ms |
| 20 days ago | Handshake completed | 408 ms |
| 20 days ago | Handshake completed | 535 ms |
| 21 days ago | Handshake completed | 430 ms |
| 23 days ago | Handshake completed | 410 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 Staats and makes no claim about it beyond what these checks measured.