Remote MCP · Endpoint

io.github.edelgad3/ai-visibility-scanner MCP server

No. io.github.edelgad3/ai-visibility-scanner answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ai-visibility-scanner-production.up.railway.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.edelgad3/ai-visibility-scanner
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
31 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Scan websites for AI visibility and marketing health with interactive dashboard.
Listing
From the official MCP registry (active).
Recent checks of io.github.edelgad3/ai-visibility-scanner
CheckedResultHandshake
1 hour agoHandshake completed31 ms
1 day agoHandshake completed38 ms
2 days agoHandshake completed27 ms
3 days agoHandshake completed32 ms
4 days agoHandshake completed47 ms
5 days agoHandshake completed59 ms
6 days agoHandshake completed45 ms
9 days agoHandshake completed40 ms
11 days agoHandshake completed51 ms
14 days agoHandshake completed99 ms
16 days agoHandshake completed36 ms
18 days agoHandshake completed36 ms
20 days agoHandshake completed29 ms
22 days agoHandshake completed66 ms
24 days agoHandshake completed34 ms
26 days agoHandshake completed34 ms
27 days agoHandshake completed29 ms
29 days agoHandshake completed24 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 io.github.edelgad3/ai-visibility-scanner and makes no claim about it beyond what these checks measured.