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.

AICompatible AI-readiness checker

REMOTE · WWW.AIOCOMPATIBLE.COM

Free checker: is a site ready for AI search? Score, AI-bot robots.txt access, issues with fixes.

+3 this week 77 Trust /100

Last scanned (20 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, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 290 tokens (~145/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

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

  • 16 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.

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 74

    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://www.aiocompatible.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.aiocompatible.com CN=YR2,O=Let's Encrypt,C=US 17 Nov 2026 15 Feb 2027 RSA 2048 SHA256-RSA 52160fc44f9b5118fb2ed680d90a3affd1e
SANs: *.aiocompatible.com, aiocompatible.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.aiocompatible.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
aiocompatible.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
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.aiocompatible.com/mcp Verified 200
http (plaintext) http://www.aiocompatible.com/mcp Inconclusive 405
MCP tools · 2 exposed · ~207 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_ai_readiness ~109

Scan a public website and return an AI-readiness score (0-100), sub-scores, AI-bot robots.txt access, and a list of issues with concrete fixes. Use when a user asks if a site is visible/optimized for ChatGPT, Perplexity, Claude, Gemini or AI search.

NameTypeReqDescription
categorystring–Optional site category; changes which schema types count as required.
urlstringyesDomain or URL to scan, e.g. example.com

No output schema declared.

No examples provided.

check_bot_access ~98

Check whether a site's robots.txt allows or blocks AI crawlers (GPTBot, PerplexityBot, ClaudeBot, Google-Extended, Applebot-Extended). Optionally limit the answer to one bot. Note: only robots.txt is checked; a firewall may still block a bot.

NameTypeReqDescription
botstring–Optional: only report this bot.
urlstringyesDomain or URL to check, e.g. example.com

No output schema declared.

No examples provided.

Install

How do I install the AICompatible AI-readiness checker MCP server?

AICompatible AI-readiness checker is a hosted endpoint at https://www.aiocompatible.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 · www.aiocompatible.com

# add to Claude Code
claude mcp add --transport http com-aiocompatible-ai-readiness 'https://www.aiocompatible.com/mcp'
Common questions

What is the AICompatible AI-readiness checker MCP server?

AICompatible AI-readiness checker is an MCP server listed in the public MCP registry as com.aiocompatible/ai-readiness. Free checker: is a site ready for AI search? Score, AI-bot robots.txt access, issues with fixes. This page covers its hosted endpoint (https://www.aiocompatible.com/mcp).

Is the AICompatible AI-readiness checker MCP server safe to use?

AICompatible AI-readiness checker 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 AICompatible AI-readiness checker MCP server expose?

AICompatible AI-readiness checker exposes 2 tools: check_ai_readiness, check_bot_access. Their descriptions and schemas cost roughly 207 tokens of context every time the server is loaded.

Does the AICompatible AI-readiness checker MCP server require authentication?

No. We connected to AICompatible AI-readiness checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AICompatible AI-readiness checker MCP server still maintained?

AICompatible AI-readiness checker 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 AICompatible AI-readiness checker MCP server?

VerifyMCP ran 12 checks on AICompatible AI-readiness checker, 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 AICompatible AI-readiness checker: 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.