Remote MCP · Endpoint
AI Visibility Audit — Can AI crawlers read and cite your site? MCP server
No. AI Visibility Audit — Can AI crawlers read and cite your site? answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://ai-visibility.rowb.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.rowb.ai-visibility/audit
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 499 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- One-call audit: robots.txt AI-bot rules, llms.txt, JSON-LD, meta tags, sitemap. Score plus fixes.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 499 ms |
| 1 day ago | Handshake completed | 451 ms |
| 2 days ago | Handshake completed | 479 ms |
| 3 days ago | Handshake completed | 443 ms |
| 4 days ago | Handshake completed | 393 ms |
| 5 days ago | Handshake completed | 662 ms |
| 6 days ago | Handshake completed | 617 ms |
| 8 days ago | Handshake completed | 427 ms |
| 11 days ago | Handshake completed | 404 ms |
| 13 days ago | Handshake completed | 456 ms |
| 15 days ago | Handshake completed | 515 ms |
| 18 days ago | Handshake completed | 433 ms |
| 20 days ago | Handshake completed | 952 ms |
| 22 days ago | Handshake completed | 410 ms |
| 24 days ago | Handshake completed | 442 ms |
| 26 days ago | Handshake completed | 409 ms |
| 27 days ago | Handshake completed | 422 ms |
| 29 days ago | Handshake completed | 514 ms |
| 29 days ago | Handshake completed | 415 ms |
The last 19 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 AI Visibility Audit — Can AI crawlers read and cite your site? and makes no claim about it beyond what these checks measured.