
Why Won't AI Mention My Product MCP server
Which MCP servers are Why Won't AI Mention My Product's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-11-02
- Registry namecom.whywontai/ai-visibilityverified in the MCP registry
The registry name sits under whywontai.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-11-02
- Tools5
- Server calls itselfwhywontai
- Server version0.1.0
- Protocol version2025-06-18
On 2026-11-02 the server answered initialize and tools/list without a sign-in. First answer in 590 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer339 ms
- Space in an agent's context≈ 711 tokensthe definitions of all its tools (5), which an agent carries on every turn
- Tool definitionsA · 97 of 100
- Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 1 of 5
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
check_robotsRead a site's robots.txt and report, for 17 search and AI crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, Googlebot, Bingbot, CCBot, Google-Extended and more), whether each may fetch the home…
scan_siteStart a full scan of a website: each page is requested separately as Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot and CCBot, compared with a rendered browser view, and scored across six SEO, AEO and GEO categories, with technical…
get_scanStatus, progress and summary of a scan: overall score and band, category scores, technical health, Domain Rating, rendering mode, platform and the top issues. Set wait_seconds (up to 25) to wait for a running scan to finish.
list_issuesAll issues found by a completed scan, most severe first, with details and example URLs. Filter by minimum severity or category.
list_scansThe API key owner's recent scans, newest first, with score and status.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"ai-visibility": {
"type": "http",
"url": "https://mcp.whywontai.com/"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http whywontai https://mcp.whywontai.com/claude.ai, ChatGPT and other clients: add https://mcp.whywontai.com/ as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.