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.

AgentsReady

REMOTE · AGENTSREADY.DEV

Audit any website for AI agents and AI search (AEO): llms.txt, AI bots, schema. Score plus fixes.

Available components

+5 this week 77 Trust /100

Last scanned (23 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 Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 563 tokens (~112/item across 5 items; 5 tools + 0 resources), lean.Pass
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (13)

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

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 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 +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.

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

  • 15 Nov 26 +2
    • MCP protocol: fail → pass ▲ functional
    • MCP protocol version: 2025-06-18 → 2026-07-28 functional
    • Server version: 1.2.2 → 1.3.0 functional
  • 14 Nov 26 0
    • Server version: 1.2.0 → 1.2.2 functional
  • 13 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 71

    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://agentsready.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentsready.dev CN=YR1,O=Let's Encrypt,C=US 11 Oct 2026 9 Jan 2027 RSA 2048 SHA256-RSA 6fee032af5495760c9083adc10d7253d200
SANs: agentsready.dev
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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 agentsready.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
agentsready.dev. 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=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentsready.dev/mcp Verified 200
http (plaintext) http://agentsready.dev/mcp HTTPS enforced 308 https://agentsready.dev/mcp
MCP tools · 5 exposed · ~523 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_site ~204

Audit a website for AI agents and AI search (AEO/GEO): scan it the way ChatGPT, Claude and Perplexity fetch it and score it 0-100 (60 core points plus 40 for the job). Checks robots.txt rules for AI bots, bot walls and firewalls, server-rendered content, structured data, llms.txt, sitemap, pricing and sign-up pages, OpenAPI and MCP. Returns the score, every failed check with its fix, and the checks it passed. Read-only scan, cached for 24 hours; it does not run an agent on the site.

NameTypeReqDescription
domainstringyesThe site to check, like example.com
jobstring–What agents should do on the site: recommend (answer questions about it), buy, signup, api (get an API key) or personal (a person's own site: who they are, their work, how to reach them). Leave out t…

No output schema declared.

No examples provided.

get_checklist ~74

The full 50-item checklist for getting recommended by AI assistants and letting their agents sign up, grouped by area, with how to pass each item. Pass kind "personal" for the list for a person's own site (portfolio, blog, GitHub Pages).

NameTypeReqDescription
kindstring–company (default) or personal

No output schema declared.

No examples provided.

get_fixes ~141

Return a ready-to-run task list for a coding agent that fixes every failed agent-readiness and AI-search check on the site (for example adding llms.txt, unblocking AI crawlers, adding structured data), biggest first, with how to verify each change. Same scan as check_site.

NameTypeReqDescription
domainstringyesThe site to check, like example.com
jobstring–What agents should do on the site: recommend (answer questions about it), buy, signup, api (get an API key) or personal (a person's own site: who they are, their work, how to reach them). Leave out t…

No output schema declared.

No examples provided.

get_standard ~45

Every check in the AgentsReady score with its points and fix: the 60 core points and the 40 points for each job (recommend, buy, signup, api, personal).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_vendor ~59

Where a software vendor ranks in the AgentsReady category rankings (CRM, help desk, payments and 17 more): score, rank, bot wall, MCP server and biggest gap.

NameTypeReqDescription
domainstringyesThe site to check, like example.com

No output schema declared.

No examples provided.

Install

How do I install the AgentsReady MCP server?

AgentsReady is a hosted endpoint at https://agentsready.dev/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 · agentsready.dev

# add to Claude Code
claude mcp add --transport http dev-agentsready-agentsready 'https://agentsready.dev/mcp'
Common questions

What is the AgentsReady MCP server?

AgentsReady is an MCP server listed in the public MCP registry as dev.agentsready/agentsready. Audit any website for AI agents and AI search (AEO): llms.txt, AI bots, schema. Score plus fixes. This page covers its hosted endpoint (https://agentsready.dev/mcp).

Is the AgentsReady MCP server safe to use?

AgentsReady 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 AgentsReady MCP server expose?

AgentsReady exposes 5 tools: check_site, get_fixes, get_checklist, get_standard, lookup_vendor. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.

Does the AgentsReady MCP server require authentication?

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

Is the AgentsReady MCP server still maintained?

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

VerifyMCP ran 13 checks on AgentsReady, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.