Remote MCP · Endpoint
Why Won't AI Mention My Product MCP server
No. Why Won't AI Mention My Product answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.whywontai.com/
The last check completed an MCP handshake.
- Registry name
- com.whywontai/ai-visibility
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 471 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- See what GPTBot, ClaudeBot and other crawlers get from a site: robots.txt checks and AI scans.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 471 ms |
| 1 day ago | Handshake completed | 391 ms |
| 2 days ago | Handshake completed | 451 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 Why Won't AI Mention My Product and makes no claim about it beyond what these checks measured.