Log inSubmit server
Agent Readiness MCP logo

Agent Readiness MCP

Scans websites for agent-readiness signals, scores ASO maturity, and generates prioritized fixes with templates.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Agent Readiness MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "agent-readiness-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@forgemeshlabs/agent-readiness-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 5 tools correctly (2d ago).

Overview

The agent-readiness-mcp MCP server scans websites for signals that affect discovery, trust, interoperability, commerce, and agent use. It returns an ASO score, maturity level, six-pillar breakdown, evidence, and recommendations across 34 checks. Developers can inspect one signal, review the scoring framework, or generate a prioritized remediation plan with templates for files and endpoints. Use it when evaluating whether a website or API is discoverable, understandable, invocable, and trustworthy for agents.

Use cases

  • Scan a website for agent-readiness gaps
  • Check a single A2A, llms.txt, or x402 signal
  • Generate a prioritized remediation plan
  • Review the ASO scoring framework
  • Inspect available readiness checks

Key features

  • 34 website readiness checks
  • ASO score and maturity level
  • Six-pillar score breakdown
  • Evidence and recommendations per check
  • Prioritized fix plans with templates
  • Local stdio deployment without credentials

Tools5

What Agent Readiness MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

11/11 checks healthy over the last 53d

What it can do

From the 5 tools this server returned when we ran it; 5 declare their own safety hints.

Makes network requests · 4Read-only tools · 5
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age137 days
Maintainers1

Observed 2026-11-02 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @forgemeshlabs/agent-readiness-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.2kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed5Callable tools this server registers over MCP.

How Agent Readiness MCP works

What agent-readiness-mcp does

The agent-readiness-mcp MCP server evaluates a website against the Agent Signal Optimization (ASO) framework. A full scan produces an Agent Readiness Report containing an overall score from 0 to 100, a maturity level, scores for six pillars, and results for 34 individual checks. Each check is reported as pass, partial, or fail with supporting evidence and a recommendation.

The checks cover discovery, content, bot access, interoperability, commerce, identity, and trust. Examples include robots.txt, sitemaps, Link headers, DNS-AID, AI-related well-known files, Markdown content negotiation, llms.txt, crawler rules, API and OAuth discovery, MCP Server Cards, Google A2A Agent Cards, Agent Skills, WebMCP, x402, MPP, UCP, ACP, machine-readable pricing, HTTPS, JSON-LD, OpenAPI, agent.json, security.txt, status endpoints, versioning, and cross-file consistency.

The score rolls up into six weighted pillars: Discoverability, Identity, Trust, Commerce, Reputation, and Memory. Maturity levels range from ASO-0 Invisible through ASO-5 Autonomous-Commerce-Ready. The results are directional self-assessments; certification requires separately verified evidence.

How it works

The MCP tools accept a website target for scanning or signal inspection. scan_site runs the complete assessment, while check_signal evaluates one named signal such as llms-txt, a2a-agent-card, or x402. list_checks helps identify available signal IDs and links them to relevant specifications. get_aso_framework explains the pillars, weights, levels, and certification thresholds without scanning a site.

get_fix_plan converts scan findings into a prioritized remediation sequence. Its output can include ready-to-paste starting points for AI crawler rules, llms.txt, agent.json, A2A and MCP cards, x402 manifests, pricing.json, security.txt, and status endpoints. The templates address the findings; they do not themselves deploy changes to the target website.

Setup and configuration

The agent-readiness-mcp MCP server requires Node.js 18 or newer. Install the published @forgemeshlabs/agent-readiness-mcp package globally, or run it directly with npx, which is the documented approach for MCP clients. The package uses local stdio transport and does not require API keys, tokens, cookies, or third-party credentials.

Claude Code can register the server with claude mcp add aso -- npx -y @forgemeshlabs/agent-readiness-mcp. Claude Desktop, Cursor, Windsurf, and other MCP clients can configure a server entry whose command is npx and whose argument is -y @forgemeshlabs/agent-readiness-mcp. Building from source is intended for scanner development and requires cloning the repository, installing dependencies, and running the build.

Tools and capabilities

  • scan_site: Run all 34 checks and return the score, level, pillar results, evidence, and recommendations.
  • get_fix_plan: Produce a prioritized remediation plan with templates for supported agent-facing files and endpoints.
  • check_signal: Test one named signal for a target website.
  • list_checks: Show the scanner catalog and specification links.
  • get_aso_framework: Return the scoring rubric and maturity model.

Limitations and notes

The agent-readiness-mcp MCP server is beta software, and its ASO scoring may change as agent standards develop. Keeping llms.txt in the scan reflects use by some non-Google agents; the documentation states that Google Search itself ignores that file. The scanner also includes browser-agent checks for semantic controls, labels, ARIA or role fallbacks, and hidden overlays.

Scanning makes outbound requests to URLs supplied by the user. The implementation only permits HTTP and HTTPS, blocks private and reserved destinations after DNS resolution, pins requests to the validated public IP, validates redirects individually, and limits redirect hops to five. The npm package does not enable public HTTP deployment; any public deployment needs authentication, per-client rate limits, request logging, and an egress policy.

The server does not modify scanned sites. Its output is an assessment and, where available, remediation guidance. Use the report as a baseline for prioritizing work rather than as proof of certification.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Agent Readiness MCP

agent-readiness-mcp is an MCP server that connects AI clients to website Agent Signal Optimization scans. Its main tools scan sites, check individual signals, list available checks, generate prioritized fix plans, and explain the ASO scoring framework, including evidence, recommendations, pillar scores, and maturity levels.

Install it with `npx -y @forgemeshlabs/agent-readiness-mcp` in an MCP client, or install the npm package globally with `npm install -g @forgemeshlabs/agent-readiness-mcp`. Node.js 18 or newer is required, and no API credentials are needed for local stdio use.

Yes, agent-readiness-mcp works with Cursor through its standard MCP configuration. Add an MCP server entry using `npx` as the command and `-y @forgemeshlabs/agent-readiness-mcp` as the argument.

Use the `check_signal` tool and provide the target website plus a signal ID such as `a2a-agent-card`, `llms-txt`, or `x402`. Use `list_checks` first when you need to discover valid signal IDs and their specification links.

No, it does not deploy changes. The `get_fix_plan` tool returns prioritized remediation guidance and ready-to-paste templates for items such as robots.txt rules, llms.txt, agent cards, pricing files, security.txt, and status endpoints.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAgent Readiness MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/agent-readiness-mcp?style=directory)](https://allmcps.com/mcp/agent-readiness-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/agent-readiness-mcp"><img src="https://allmcps.com/api/badge/agent-readiness-mcp?style=directory" alt="Agent Readiness MCP on AllMCPs" /></a>