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
265 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
See whether ChatGPT, Claude and Gemini recommend a startup's product, and who they name instead.
Listing
From the official MCP registry (active).
Recent checks of com.frontstat/visibility
CheckedResultHandshake
2 hours agoHandshake completed265 ms
2 days agoHandshake completed201 ms
4 days agoHandshake completed181 ms
7 days agoHandshake completed283 ms
9 days agoHandshake completed178 ms
11 days agoHandshake completed176 ms
13 days agoHandshake completed181 ms
15 days agoHandshake completed251 ms
16 days agoHandshake completed212 ms
18 days agoHandshake completed272 ms
19 days agoHandshake completed248 ms
20 days agoHandshake completed204 ms
23 days agoHandshake completed88 ms
24 days agoHandshake completed106 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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.