Remote MCP · Endpoint
com.frontstat/visibility MCP server
No. com.frontstat/visibility answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://frontstat.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.frontstat/visibility
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 189 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 92.9% from 14 checks
- Described by its publisher as
- See whether ChatGPT, Claude and Gemini recommend a startup's product, and who they name instead.
- Website
- https://frontstat.com/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 189 ms |
| 10 days ago | Handshake completed | 176 ms |
| 11 days ago | Handshake completed | 239 ms |
| 11 days ago | Handshake completed | 174 ms |
| 13 days ago | Handshake completed | 278 ms |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 15 days ago | Handshake completed | 338 ms |
| 16 days ago | Handshake completed | 620 ms |
| 17 days ago | Handshake completed | 187 ms |
| 19 days ago | Handshake completed | 175 ms |
| 22 days ago | Handshake completed | 265 ms |
| 24 days ago | Handshake completed | 201 ms |
| 26 days ago | Handshake completed | 181 ms |
| 29 days ago | Handshake completed | 283 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 24.
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 com.frontstat/visibility and makes no claim about it beyond what these checks measured.