Remote MCP · Endpoint

RankRoot: AI visibility audit MCP server

No. RankRoot: AI visibility audit answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://getrankroot.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.zachhhhh/rankroot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
830 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Audit a site's visibility to ChatGPT, Perplexity, Claude and AI agents. Generates llms.txt.
Listing
From the official MCP registry (active).
Recent checks of RankRoot: AI visibility audit
CheckedResultHandshake
1 hour agoHandshake completed830 ms
4 days agoHandshake completed1.36 s
7 days agoHandshake completed850 ms
16 days agoHandshake completed922 ms
16 days agoHandshake completed1.40 s
18 days agoHandshake completed800 ms
19 days agoHandshake completed873 ms
20 days agoHandshake completed1.04 s
21 days agoHandshake completed952 ms
22 days agoHandshake completed887 ms
23 days agoHandshake completed985 ms
26 days agoHandshake completed1.83 s
29 days agoHandshake completed1.13 s

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

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 RankRoot: AI visibility audit and makes no claim about it beyond what these checks measured.