Skip to content

agentready MCP server

io.github.msanchezgrice/agentreadymsanchezgricestreamable-httpv1.0.0Scanned

Scan any public site for AI-agent visibility; get scored findings, a machine-readable fix pack, and

7 tools: 3 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 3 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 4
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the agentready MCP server can do

The agentready MCP server is published by the GitHub account msanchezgrice. It has 7 tools. It can create or change data (3 tools: scan_url, verify_fixes and audit_openapi_readiness), but cannot delete data. 4 tools only read.

1 tool reads private data (get_fix_pack); 2 tools bring in text other people can write (get_fix_pack and check_crawler_access); 4 tools can send data out of your system (scan_url, get_fix_pack, verify_fixes and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 3Claude Code: ask
  • audit_openapi_readinessStatically inspect an OpenAPI 3.0 or 3.1 JSON object or JSON string for operation identity, auth and scopes, errors, examples, retries, limits, lifecycle, pagination, and workflows…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Statically inspect an OpenAPI 3.0 or 3.1 JSON object or JSON string for operation identity, auth and scopes, errors, examples, retries, limits, lifecycle, pagination, and workflows. No API operation is executed.
  • scan_urlRun an AgentReady scan of a public URL.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Run an AgentReady scan of a public URL. Returns the 0-100 score, per-phase findings, top priorities, and the Fix Pack v2 implementation contract. Repository paths remain candidate targets until a connected-repository resolver proves them.
  • verify_fixesRe-scan a public URL and evaluate fix-specific stable ids from a previous v1 or v2 Fix Pack.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Re-scan a public URL and evaluate fix-specific stable ids from a previous v1 or v2 Fix Pack. A fix closes when its finding id is absent; score delta is secondary evidence only.
Only reads 4Show 4 read-only tools
  • check_crawler_accessFetch robots.txt and a bounded public page through validated redirects, then inspect named-token path rules, final delivery, X-Robots-Tag, and HTML meta robots.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "html": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Fetch robots.txt and a bounded public page through validated redirects, then inspect named-token path rules, final delivery, X-Robots-Tag, and HTML meta robots. Named-bot edge/WAF treatment remains unobservable.
  • get_fix_packScan a public URL and return Fix Pack v2: prioritized fixes with stable ids, observed evidence, candidate target URLs and repository paths, review gates, and fix-specific acceptanc…Reads private dataReads text others writeCan send data outNo findings

    Why it is in this group

    • The name "get_fix_pack" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Scan a public URL and return Fix Pack v2: prioritized fixes with stable ids, observed evidence, candidate target URLs and repository paths, review gates, and fix-specific acceptance assertions for a coding agent.
  • get_public_reportRead the latest saved public scan report or bounded history using its opaque report id.No findings

    Why it is in this group

    • The name "get_public_report" says "get": a word for reading.
    Description, as the server wrote it
    Read the latest saved public scan report or bounded history using its opaque report id. Reports are only created after explicit opt-in and expire after 30 days.
  • validate_a2a_agent_cardStatically validate an A2A Agent Card JSON object.No findings

    Why it is in this group

    • The name "validate_a2a_agent_card" says "validate": a word for reading.
    Description, as the server wrote it
    Statically validate an A2A Agent Card JSON object. Strict-current evidence and legacy interoperability are reported separately; no agent endpoint or skill is invoked.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

8 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out4
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__agentready__get_fix_pack"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:08 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.agentready.me/api/mcp: tools/list returned 7 tools to an anonymous client, including scan_url (write), verify_fixes (write), audit_openapi_readiness (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agentready https://www.agentready.me/api/mcp
claude mcp add --transport http agentready https://www.agentready.me/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agentready__get_public_report",
      "mcp__agentready__validate_a2a_agent_card"
    ],
    "ask": [
      "mcp__agentready__scan_url",
      "mcp__agentready__get_fix_pack",
      "mcp__agentready__verify_fixes",
      "mcp__agentready__check_crawler_access",
      "mcp__agentready__audit_openapi_readiness"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agentready. Review it before you use it.

Capability tags behind 4 rules
  • mcp__agentready__scan_url outbound
  • mcp__agentready__get_fix_pack private-data, untrusted-input, outbound
  • mcp__agentready__verify_fixes outbound
  • mcp__agentready__check_crawler_access untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.msanchezgrice/agentready/verify?hash=f94f5c17c79a9388c47e689a77741128a44e6aadfdcfe525a149574d447e7e95" | jq -e '.changed == false'

Pinned hash f94f5c17c79a, from Nov 20, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.msanchezgrice/agentready/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.msanchezgrice/agentready
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.msanchezgrice/agentready.svg)](https://radar.anlyon.com/servers/io.github.msanchezgrice/agentready)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:42 UTC.

agentready MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the agentready MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the agentready MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the agentready MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the agentready MCP server have?

7 tools: 3 write, 4 read. scan_url, verify_fixes, audit_openapi_readiness, get_fix_pack, get_public_report, check_crawler_access and validate_a2a_agent_card.

Does the agentready MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the agentready MCP server send data to outside services?

4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_url, get_fix_pack, verify_fixes and check_crawler_access.

Has the agentready MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.