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.

AISeeWhy

REMOTE · API.AISEEWHY.COM

Can ChatGPT, Claude and Perplexity crawlers read your page? Audit, fixes, compare, monitoring.

Available components

+3 this week 77 Trust /100

Last scanned (13 hours ago)

Scores higher than 67% 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 Security80
  • 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3060 tokens (~153/item across 20 items; 19 tools + 1 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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "generate_content_merge_plan" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

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

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.

  • 21 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1253 → 3060 ▼ functional
    • Schema quality: 1253 → 1452 ▼ functional
    • First check of Capabilities: pass functional
    • First check of Schema quality: 100 functional
    • Destructive annotations: pass → 0 functional
    • New resource “ai-crawler-check” functional
    • Server version: 1.1.0 → 1.2.0 functional
    • New tool “detect_keyword_cannibalization” functional
    • New tool “find_content_consolidation_candidates” functional
    • New tool “find_declining_pages” functional
    • New tool “find_high_impression_low_ctr_pages” functional
    • New tool “find_zero_click_pages” functional
    • New tool “generate_content_merge_plan” functional
    • New tool “generate_redirect_plan” functional
    • New tool “get_all_pages_performance” functional
    • New tool “identify_strongest_page” functional
    • New tool “prioritize_seo_opportunities” functional
    • New tool “show_ai_crawler_check” functional
    • “audit_sitemap” reworded the description of “language” cosmetic
    • “audit_url” reworded the description of “language” cosmetic
    • “compare_urls” reworded the description of “language” cosmetic
    • “crawl_site” reworded the description of “language” cosmetic
    • “explain_finding” reworded the description of “language” cosmetic
  • 20 Nov 26 +1

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

  • 18 Nov 26 0
    • Tool “crawl_site” rewrote its description, which is the text the model reads security
  • 17 Nov 26 +1

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

  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “audit_url” rewrote its description, which is the text the model reads security
    • Schema quality: 131 → 157 ▼ functional
    • New tool “crawl_site” functional
    • New tool “find_broken_links” functional
  • 14 Nov 26 +1

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

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 73

    First indexed and scored.

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://api.aiseewhy.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aiseewhy.com CN=YE1,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA384 5969af1c02d902b18f91d89d76ba5193da7
SANs: *.aiseewhy.com, aiseewhy.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.aiseewhy.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
aiseewhy.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.aiseewhy.com/mcp Verified 200
http (plaintext) http://api.aiseewhy.com/mcp HTTPS enforced 301 https://api.aiseewhy.com/mcp
MCP tools · 19 exposed · ~2,849 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
audit_sitemap ~133

Audit up to 10 pages listed in a sitemap or sitemap index. Returns one summary line per page plus the full report of every page with findings. Needs an API key.

NameTypeReqDescription
language––Report language as a code such as en, de, fr, es, ja or zh. Defaults to the account language (English without a key); 60 languages are supported.
max_urlsinteger–How many page URLs from the sitemap to audit, 1 to 10.
sitemap_urlstringyesURL of a sitemap.xml or sitemap index, for example https://example.com/sitemap.xml.
NameTypeReqDescription
resultstringyes–

No examples provided.

audit_url ~213

Audit one URL: fetch it as 16 AI and search crawlers plus curl and a browser, check robots.txt, structured data, answer-first content, freshness, hreflang and llms.txt, plus classic on-page SEO (title, meta description, H1, canonical, noindex, image alt text, broken links). Returns a Markdown report with findings and fixes. language: report language code (en, de, ja, …).

NameTypeReqDescription
bots––Only test these crawlers, by name (for example GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended). Omit to test all 16 AI and search crawlers.
language––Report language as a code such as en, de, fr, es, ja or zh. Defaults to the account language (English without a key); 60 languages are supported.
urlstringyesPage to audit: a full URL or a bare domain such as example.com (https is assumed).
NameTypeReqDescription
resultstringyes–

No examples provided.

compare_urls ~123

Audit 2 or 3 URLs (yours and competitors') and compare them side by side: score, P1/P2/P3 counts, blocked crawlers, llms.txt, structured data, text without JavaScript. Needs an API key.

NameTypeReqDescription
language––Report language as a code such as en, de, fr, es, ja or zh. Defaults to the account language (English without a key); 60 languages are supported.
urlsarrayyes2 or 3 page URLs or domains to compare; put your own page first.
NameTypeReqDescription
resultstringyes–

No examples provided.

crawl_site ~193

SEO site audit: crawl up to 50 pages (up to 90 seconds) of a site from a start page by following internal links (then the sitemap), as a browser and respecting robots.txt. Reports broken and redirected internal links, duplicate titles and descriptions, orphan, deep and thin pages, sitemap entries that are noindex, redirect or name another canonical, and on-page SEO problems counted across pages. Needs an API key.

NameTypeReqDescription
language––Report language as a code such as en, de, fr, es, ja or zh. Defaults to the account language (English without a key); 60 languages are supported.
max_pagesinteger–How many pages to crawl, 1 to 50.
urlstringyesStart page of the crawl, usually the home page: a full URL or a bare domain such as example.com. Only pages on the same host are crawled.
NameTypeReqDescription
resultstringyes–

No examples provided.

detect_keyword_cannibalization ~147

Groups of URLs competing for the same search queries: shared queries, intent and content similarity, the primary page, the recommended action and a confidence score. Separates harmful cannibalization from legitimate multiple rankings. Uses your connected Google Search Console (read-only) plus a crawl of the site; the analysis is reused for a day. Never changes your site: redirects are proposals only. Needs an API key from a paid plan.

NameTypeReqDescription
limitinteger–Rows to return, 1 to 200.
site––Search Console property, for example sc-domain:example.com or https://example.com/. Omit to use the site of your latest Page Intelligence analysis.
NameTypeReqDescription
resultstringyes–

No examples provided.

explain_finding ~121

Explain a finding id (e.g. access.blocked, robots.disallowed, schema.software_no_offers) in the given language: what it means, why it matters for AI search and how to fix it.

NameTypeReqDescription
finding_idstringyesFinding id exactly as shown in an audit report, for example access.blocked or llms.missing.
language––Report language as a code such as en, de, fr, es, ja or zh. Defaults to the account language (English without a key); 60 languages are supported.
NameTypeReqDescription
resultstringyes–

No examples provided.

find_broken_links ~195

Broken link finder: read a page and the pages of the same site it links to, level by level (depth 0 is the start page only; up to 50 pages and 90 seconds), and check every link found once: pages, other sites and images. Returns the broken links with the link text and the pages that contain them, apart from links that could not be verified (blocked, rate limited, slow) and redirects. Respects robots.txt for pages it walks into. Needs an API key.

NameTypeReqDescription
depthinteger–Levels of pages to follow from the start page, 0 to 3.
max_pagesinteger–How many pages to read, 1 to 50.
urlstringyesStart page: a full URL or a bare domain such as example.com. Only pages on the same host are walked; links to other sites are checked but not followed.
NameTypeReqDescription
resultstringyes–

No examples provided.

find_content_consolidation_candidates ~139

Groups of pages that should be merged or redirected into a stronger page, with what to do with each competing page and why. Pages with a distinct intent are kept. Uses your connected Google Search Console (read-only) plus a crawl of the site; the analysis is reused for a day. Never changes your site: redirects are proposals only. Needs an API key from a paid plan.

NameTypeReqDescription
limitinteger–Rows to return, 1 to 200.
site––Search Console property, for example sc-domain:example.com or https://example.com/. Omit to use the site of your latest Page Intelligence analysis.
NameTypeReqDescription
resultstringyes–

No examples provided.

find_declining_pages ~142

Pages losing organic clicks against the previous comparable period, with the likely cause (ranking loss, lower demand, cannibalization, CTR loss, technical indexing, outdated content) and the action. Uses your connected Google Search Console (read-only) plus a crawl of the site; the analysis is reused for a day. Never changes your site: redirects are proposals only. Needs an API key from a paid plan.

NameTypeReqDescription
limitinteger–Rows to return, 1 to 200.
site––Search Console property, for example sc-domain:example.com or https://example.com/. Omit to use the site of your latest Page Intelligence analysis.
NameTypeReqDescription
resultstringyes–

No examples provided.

find_high_impression_low_ctr_pages ~142

Pages Google shows often that users rarely click, with the query, the position, the CTR that is normal there and what is wrong with the title, description or query match. Uses your connected Google Search Console (read-only) plus a crawl of the site; the analysis is reused for a day. Never changes your site: redirects are proposals only. Needs an API key from a paid plan.

NameTypeReqDescription
limitinteger–Rows to return, 1 to 200.
site––Search Console property, for example sc-domain:example.com or https://example.com/. Omit to use the site of your latest Page Intelligence analysis.
NameTypeReqDescription
resultstringyes–

No examples provided.

find_zero_click_pages ~168

Pages with zero recorded clicks in the last 90 days, each with a verdict (KEEP, OPTIMIZE, MERGE, REDIRECT or REVIEW FOR REMOVAL) and the evidence. A trigger for review, never for automatic deletion; pages Search Console returned nothing for are reported as unknown, not as zero. Uses your connected Google Search Console (read-only) plus a crawl of the site; the analysis is reused for a day. Never changes your site: redirects are proposals only. Needs an API key from a paid plan.

NameTypeReqDescription
limitinteger–Rows to return, 1 to 200.
site––Search Console property, for example sc-domain:example.com or https://example.com/. Omit to use the site of your latest Page Intelligence analysis.
NameTypeReqDescription
resultstringyes–

No examples provided.

generate_content_merge_plan ~139

For each consolidation group: the content and queries to move into the target page, improvements to the target, internal links to update, sitemap and canonical changes and a validation plan. Uses your connected Google Search Console (read-only) plus a crawl of the site; the analysis is reused for a day. Never changes your site: redirects are proposals only. Needs an API key from a paid plan.

NameTypeReqDescription
limitinteger–Rows to return, 1 to 200.
site––Search Console property, for example sc-domain:example.com or https://example.com/. Omit to use the site of your latest Page Intelligence analysis.
NameTypeReqDescription
resultstringyes–

No examples provided.

generate_redirect_plan ~164

A 301 redirect plan for redundant pages: source, destination, reason, Search Console evidence, intent similarity, confidence, risk, required content migration and internal links to update. Detects chains, loops, canonical conflicts and irrelevant destinations. Proposals only: nothing is executed and every redirect needs your approval. Uses your connected Google Search Console (read-only) plus a crawl of the site; the analysis is reused for a day. Never changes your site: redirects are proposals only. Needs an API key from a paid plan.

NameTypeReqDescription
limitinteger–Rows to return, 1 to 200.
site––Search Console property, for example sc-domain:example.com or https://example.com/. Omit to use the site of your latest Page Intelligence analysis.
NameTypeReqDescription
resultstringyes–

No examples provided.

get_all_pages_performance ~198

Every page of the site with clicks, impressions, CTR, position, trend, page category (winner, zero click, high impressions low CTR, declining, cannibalized, not indexable) and recommended action. Uses your connected Google Search Console (read-only) plus a crawl of the site; the analysis is reused for a day. Never changes your site: redirects are proposals only. Needs an API key from a paid plan.

NameTypeReqDescription
category––Only pages in this category: winner, zero_click, high_impressions_low_ctr, declining, cannibalized, low_traffic, not_indexable, no_data.
limitinteger–Rows to return, 1 to 200.
site––Search Console property, for example sc-domain:example.com or https://example.com/. Omit to use the site of your latest Page Intelligence analysis.
sortstring–clicks, impressions or position.
NameTypeReqDescription
resultstringyes–

No examples provided.

identify_strongest_page ~169

The strongest URL of each group of competing pages, scored on clicks, history, query coverage, ranking stability, intent match, content, internal links, canonical setup and business value, with every component shown (the page with the most clicks does not always win). Uses your connected Google Search Console (read-only) plus a crawl of the site; the analysis is reused for a day. Never changes your site: redirects are proposals only. Needs an API key from a paid plan.

NameTypeReqDescription
limitinteger–Rows to return, 1 to 200.
site––Search Console property, for example sc-domain:example.com or https://example.com/. Omit to use the site of your latest Page Intelligence analysis.
url––Only the group that contains this URL.
NameTypeReqDescription
resultstringyes–

No examples provided.

list_watched_sites ~33

List the URLs this account monitors, with the frequency, last score and last check time. Needs an API key.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

prioritize_seo_opportunities ~155

A ranked P1-P3 action queue to grow organic traffic from existing pages (consolidate, fix snippets, recover declines, fix indexing, add internal links) with a transparent score, exact steps and impact split into measured numbers and labelled estimates. Uses your connected Google Search Console (read-only) plus a crawl of the site; the analysis is reused for a day. Never changes your site: redirects are proposals only. Needs an API key from a paid plan.

NameTypeReqDescription
limitinteger–Rows to return, 1 to 200.
site––Search Console property, for example sc-domain:example.com or https://example.com/. Omit to use the site of your latest Page Intelligence analysis.
NameTypeReqDescription
resultstringyes–

No examples provided.

show_ai_crawler_check ~171

Check one page for AI crawlers and AI search (the same check and limits as audit_url) and show the result as a visual card in apps that render one (ChatGPT, Claude): the score, which AI crawlers are let in or blocked, the costliest finding with its fix and how many findings are locked, by priority. Use it when the user wants to see a site's AI crawler access at a glance; use audit_url for a Markdown report.

NameTypeReqDescription
language––Report language as a code such as en, de, fr, es, ja or zh. Defaults to the account language (English without a key); 60 languages are supported.
urlstringyesPage to audit: a full URL or a bare domain such as example.com (https is assumed).
NameTypeReqDescription
accessarray–One row per AI crawler: bot, cls, status, verdict.
counts––Findings per priority, P1 to P3, of the whole report.
domainstringyesHost of the checked page.
fullbooleanyesTrue: every finding is in findings. False: a preview, the rest only by priority.
lead––The costliest finding with its fixes, the one the preview opens.
linksobjectyesreport: the page on aiseewhy.com; example: a sample full report.
locked_countsobject–Findings not shown, per priority.
note––Why no new check ran (the site was checked before), or null.
score––value 0-100 and visible: whether AI crawlers and AI search can read the page.
tone––Score ring tone: ok, p2 or p1.

No examples provided.

watch_site ~104

Add a URL to the account's scheduled monitoring (freq: daily or weekly). The owner gets an email when a check finds a new P1 problem or the score drops by 10 or more. Needs an API key; adding the same URL again only changes the frequency.

NameTypeReqDescription
freqstring–How often to check the page: daily or weekly (default).
urlstringyesPage to monitor: a full URL or a bare domain such as example.com.
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the AISeeWhy MCP server?

AISeeWhy is a hosted endpoint at https://api.aiseewhy.com/mcp, 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 · api.aiseewhy.com

# add to Claude Code
claude mcp add --transport http com-aiseewhy-aiseewhy 'https://api.aiseewhy.com/mcp'
Common questions

What is the AISeeWhy MCP server?

AISeeWhy is an MCP server listed in the public MCP registry as com.aiseewhy/aiseewhy. Can ChatGPT, Claude and Perplexity crawlers read your page? Audit, fixes, compare, monitoring. This page covers its hosted endpoint (https://api.aiseewhy.com/mcp).

Is the AISeeWhy MCP server safe to use?

AISeeWhy scores 77 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 AISeeWhy MCP server expose?

AISeeWhy exposes 19 tools: show_ai_crawler_check, audit_url, audit_sitemap, explain_finding, compare_urls, and 14 more. Their descriptions and schemas cost roughly 2,849 tokens of context every time the server is loaded.

Does the AISeeWhy MCP server require authentication?

No. We connected to AISeeWhy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AISeeWhy MCP server still maintained?

AISeeWhy 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 AISeeWhy MCP server?

VerifyMCP ran 14 checks on AISeeWhy, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. 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.