Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Why Won't AI Mention My Product

REMOTE · MCP.WHYWONTAI.COM

See what GPTBot, ClaudeBot and other crawlers get from a site: robots.txt checks and AI scans.

+3 this week 76 Trust /100

Last scanned (16 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security71
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1526 tokens (~127/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1139 → 1526 ▼ functional
    • New tool “get_bing_ai_citations” functional
    • New tool “get_index_status” functional
    • New tool “get_page_two” functional
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 857 → 1139 ▼ functional
    • New tool “get_long_questions” functional
    • New tool “get_plan_pass_quote” functional
  • 11 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_internal_links” rewrote its description, which is the text the model reads security
    • Tool “list_scans” rewrote its description, which is the text the model reads security
    • Tool “scan_site” rewrote its description, which is the text the model reads security
    • Schema quality: 737 → 857 ▼ functional
    • New tool “check_agent_listings” functional
  • 10 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 629 → 737 ▼ functional
    • New tool “get_internal_links” functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.whywontai.com/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=whywontai.com CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 ee036403b26178e513d3ad5be418a686
SANs: whywontai.com, mcp.whywontai.com, *.mcp.whywontai.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.whywontai.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
whywontai.com. DS published 2371 13 Verified
mcp.whywontai.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.whywontai.com/ Verified 200
http (plaintext) http://mcp.whywontai.com/ Inconclusive 405
MCP tools · 12 exposed · ~1,317 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_agent_listings ~167

Check whether a product can be listed in AI agent directories: the official MCP Registry, the Claude Connectors Directory, ChatGPT apps (OpenAI plugin directory), skills.sh and Manus. Looks for the site's remote MCP server, its auth (OAuth discovery, Dynamic Client Registration, S256 PKCE), tool titles and hints, existing MCP Registry entries, privacy and terms links, llms.txt and agent card. Returns each directory's status, blockers and next steps. Works without an API key (limited per day).

NameTypeReqDescription
mcp_urlstring–Optional. The MCP server URL if it is not at mcp.<domain>, <domain>/mcp or <domain>/api/mcp.
urlstringyesThe product's site, e.g. example.com

No output schema declared.

No examples provided.

check_robots ~154

Read 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 page and an optional path, and which rule decides. Uses RFC 9309 matching. Works without an API key (limited per day).

NameTypeReqDescription
pathstring–Optional path to check as well, e.g. /blog/post. Defaults to the path in url.
urlstringyesSite or page address, e.g. example.com or https://example.com/pricing

No output schema declared.

No examples provided.

get_bing_ai_citations ~125

Bing Webmaster Tools AI Performance for one of the user's sites (paid plans; data comes from the whywontai Chrome extension or a CSV upload): the grounding queries Microsoft Copilot and Bing AI used to find the site, with intent, topic, citations, citation share and the pages cited. Flags buying queries (Commercial, Comparison, Transactional, Shopping) cited to a weaker page, queries split across two own pages, low citation share and drops since the earlier period. Read-only.

NameTypeReqDescription
domainstringyesThe site, e.g. example.com

No output schema declared.

No examples provided.

get_index_status ~80

Google index status of the user's site pages from the stored URL Inspection checks (paid plans): counts of indexed and not indexed pages, the not-indexed pages grouped by reason with the fix for each reason. Read-only. New checks run weekly and from the dashboard Indexing tab.

NameTypeReqDescription
domainstringyesThe site, e.g. example.com

No output schema declared.

No examples provided.

get_internal_links ~102

The newest internal link plan for one of the user's sites (paid plans): where words already on one page should link to another page, with the Search Console query and average position behind each anchor. Targets at position 4 to 15 come first. Read-only; the owner approves and applies links from the whywontai.com dashboard.

NameTypeReqDescription
domainstringyesThe site, e.g. example.com
limitinteger–Default 25.

No output schema declared.

No examples provided.

get_long_questions ~163

Search Console queries of 8 or more words for one of the user's sites (paid plans, Search Console connected): full questions, the same ones people ask ChatGPT. Returns each question with impressions, clicks, CTR, average position, question kind and the page that ranks, and 'targets': the pages that rank at position 20 or better with low CTR, each with the questions to answer in a short block at the top of that page. Read-only.

NameTypeReqDescription
daysinteger–Default 90.
domainstringyesThe site, e.g. example.com
limitinteger–Questions to return. Default 25.
min_wordsinteger–Default 8. Use 6 for a new site with little data.

No output schema declared.

No examples provided.

get_page_two ~115

Search Console queries where one of the user's sites ranks on page 2 of Google (average position 11 to 20), grouped by the page that ranks (paid plans, Search Console connected). Each page has its queries, impressions, clicks, an estimate of extra clicks at position 8, whether the title has the query words, and the actions to move it to page 1. Read-only.

NameTypeReqDescription
daysinteger–Default 28.
domainstringyesThe site, e.g. example.com

No output schema declared.

No examples provided.

get_plan_pass_quote ~75

The user's current plan and the price of each prepaid plan pass (Starter, Pro, Agency; 1 month or 1 year), with whether the account can buy it and until when it would run. Takes no payment and changes nothing.

NameTypeReqDescription
productstring–Optional. One product id. Default: all products.

No output schema declared.

No examples provided.

get_scan ~97

Status, 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.

NameTypeReqDescription
scan_idstringyesscan_id from scan_site or list_scans
wait_secondsinteger–Wait up to this long for the scan to complete. Default 0.

No output schema declared.

No examples provided.

list_issues ~98

All issues found by a completed scan, most severe first, with details and example URLs. Filter by minimum severity or category.

NameTypeReqDescription
categorystring–e.g. body_copy, crawl_render, intent_match, internal_linking, demand_capture, ai_citability
limitinteger–Default 25.
min_severitystring–Only issues at this severity or worse.
scan_idstringyes–

No output schema declared.

No examples provided.

list_scans ~44

The user's recent scans, newest first, with score and status.

NameTypeReqDescription
domainstring–Only scans of this domain.
limitinteger–Default 10.

No output schema declared.

No examples provided.

scan_site ~97

Start a full scan of a public website that the user names. The scan requests each page the way common search and AI crawlers do, compares each response with a rendered browser view, and scores six SEO, AEO and GEO categories. Each scan counts against the user's monthly plan quota. Returns a scan_id. A scan takes 1 to 5 minutes.

NameTypeReqDescription
urlstringyesSite to scan, e.g. example.com

No output schema declared.

No examples provided.

Install

How do I install the Why Won't AI Mention My Product MCP server?

Why Won't AI Mention My Product is a hosted endpoint at https://mcp.whywontai.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.whywontai.com

# add to Claude Code
claude mcp add --transport http com-whywontai-ai-visibility 'https://mcp.whywontai.com/'
Common questions

What is the Why Won't AI Mention My Product MCP server?

Why Won't AI Mention My Product is an MCP server listed in the public MCP registry as com.whywontai/ai-visibility. See what GPTBot, ClaudeBot and other crawlers get from a site: robots.txt checks and AI scans. This page covers its hosted endpoint (https://mcp.whywontai.com/).

Is the Why Won't AI Mention My Product MCP server safe to use?

Why Won't AI Mention My Product scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Why Won't AI Mention My Product MCP server expose?

Why Won't AI Mention My Product exposes 12 tools: check_robots, check_agent_listings, scan_site, get_scan, list_issues, and 7 more. Their descriptions and schemas cost roughly 1,317 tokens of context every time the server is loaded.

Does the Why Won't AI Mention My Product MCP server require authentication?

No. We connected to Why Won't AI Mention My Product without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Why Won't AI Mention My Product MCP server still maintained?

Why Won't AI Mention My Product is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Why Won't AI Mention My Product MCP server?

VerifyMCP ran 12 checks on Why Won't AI Mention My Product, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Why Won't AI Mention My Product: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.