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.

AnswerRail AEO, Schema.org & /llms.txt Audit MCP

REMOTE · ANSWERRAIL.COM · 2 COMPONENTS

6-category AI readiness, Schema.org, robots.txt, /llms.txt & 25k-token audit + auto-fix MCP server

72 Trust /100

Last scanned (23 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Web Scraping

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 Security74
Transport & Reachability100
Schema Quality & AI Usability83
  • 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 798 tokens (~133/item across 6 items; 4 tools + 2 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 Management20
  • Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 29 Oct 26 69

    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 4 Nov 2026 · Probed https://answerrail.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=answerrail.com CN=YE1,O=Let's Encrypt,C=US 1 Oct 2026 30 Dec 2026 ECDSA 256 ECDSA-SHA384 6555b6e07e89d25c040e36319ac690660eb
SANs: *.answerrail.com, answerrail.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 answerrail.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
answerrail.com. absent 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://answerrail.com/mcp Verified 200
http (plaintext) http://answerrail.com/mcp HTTPS enforced 301 https://answerrail.com/mcp
MCP tools · 4 exposed · ~710 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_ai_readiness ~201

Audits a website URL or domain for AI crawler access (GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot), 25,000-token HTML RAG truncation, /llms.txt presence, Schema.org JSON-LD entities, and Google Lighthouse 13.5 Agentic Browsing (/.well-known/ai-catalog.json ARD 1.0). Use this tool first when diagnosing why a site is omitted or misquoted by ChatGPT, Perplexity, or Claude. Do not use this tool to extract full-page Markdown content (use extract_byte0_markdown instead) or to generate static manifest files (use generate_ai_manifests instead). Read-only network check; requires no API key.

NameTypeReqDescription
urlstringyesFully qualified HTTPS URL or bare domain name to audit (e.g., "https://stripe.com/pricing" or "example.com"). Defaults to HTTPS if scheme is omitted.

No output schema declared.

No examples provided.

extract_byte0_markdown ~160

Strips React/Next.js hydration scripts, Shopify Liquid/WordPress DOM bloat, and inline SVGs/CSS from any URL, returning clean Byte-0 GitHub-Flavored Markdown (GFM) with front-loaded Schema.org tables. Use this tool when you need to read a web page or pricing table inside an LLM context window without exceeding the 25,000-token truncation limit. Do not use this tool if you only need a diagnostic readiness score or robots.txt check (use audit_ai_readiness instead). Read-only HTTP extraction; requires no API key.

NameTypeReqDescription
urlstringyesFully qualified URL of the web page to convert into Byte-0 Markdown (e.g., "https://vercel.com/pricing").

No output schema declared.

No examples provided.

generate_ai_manifests ~147

Compiles ready-to-save /llms.txt documentation index and Google Lighthouse 13.5 /.well-known/ai-catalog.json (ARD 1.0) JSON manifests from a live domain, plus HTML <head> and robots.txt Agentmap snippets. Use this tool when a developer wants to remediate missing discovery manifests identified by audit_ai_readiness. Do not use this tool for general web scraping (use extract_byte0_markdown instead). Read-only synthesis; requires no API key and does not modify remote servers.

NameTypeReqDescription
domainstringyesTarget domain name or root URL to generate manifests for (e.g., "example.com" or "https://example.com").

No output schema declared.

No examples provided.

query_truncation_benchmark ~202

Retrieves empirical benchmark telemetry from the 2026 50-Site SaaS & E-Commerce AI Truncation Study (measuring raw HTML token weight, 25,000-token Perplexity/ChatGPT cutoff truncation, visible price omission, /llms.txt adoption, and Lighthouse 13.5 ARD 1.0 adoption). Use this tool when comparing a site against industry peers (such as Stripe, Vercel, Datadog, or Shopify) or answering research questions about the Static /llms.txt Paradox. Do not use this tool to run a live scan on an arbitrary unbenchmarked URL (use audit_ai_readiness instead). Read-only benchmark lookup; requires no API key.

NameTypeReqDescription
domainstring–Optional domain name (e.g., "stripe.com" or "vercel.com") to filter the benchmark study. Omit or pass empty string to return the full 50-site statistical summary.

No output schema declared.

No examples provided.

Install

How do I install the AnswerRail AEO, Schema.org & /llms.txt Audit MCP server?

AnswerRail AEO, Schema.org & /llms.txt Audit MCP is a hosted endpoint at https://answerrail.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 · answerrail.com

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

What is the AnswerRail AEO, Schema.org & /llms.txt Audit MCP server?

AnswerRail AEO, Schema.org & /llms.txt Audit MCP is listed in the public MCP registry as io.github.quitegoodproject/answerrail-mcp. 6-category AI readiness, Schema.org, robots.txt, /llms.txt & 25k-token audit + auto-fix MCP server. This page covers its hosted endpoint (https://answerrail.com/mcp).

Is the AnswerRail AEO, Schema.org & /llms.txt Audit MCP server safe to use?

AnswerRail AEO, Schema.org & /llms.txt Audit MCP scores 72 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 AnswerRail AEO, Schema.org & /llms.txt Audit MCP server expose?

AnswerRail AEO, Schema.org & /llms.txt Audit MCP exposes 4 tools: audit_ai_readiness, generate_ai_manifests, extract_byte0_markdown, query_truncation_benchmark. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.

Does the AnswerRail AEO, Schema.org & /llms.txt Audit MCP server require authentication?

No. We connected to AnswerRail AEO, Schema.org & /llms.txt Audit MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AnswerRail AEO, Schema.org & /llms.txt Audit MCP server still maintained?

AnswerRail AEO, Schema.org & /llms.txt Audit MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.