Agent Ready

io.github.mlava由 GitHub 账号 mlava 发布v0.7.7更新于 Nov 2, 2026

Scan any URL for AI agent readability — Vercel Spec, llmstxt.org, and agent-protocol manifests.

已验证Streamable HTTP可网页运行网页搜索与抓取开发者工具

概览

AI 生成的概览

扫描网址的 AI 智能体可读性,依据 Vercel 规范、llmstxt.org 与智能体协议清单给出评分和逐项修复提示。

可以做什么
  • 扫描站点或页面,返回 Vercel 与 llms.txt 评分、逐项检查结果及修复建议
  • 按 id 获取此前运行的扫描结果
  • 校验来自网址或粘贴内容的 JSON-LD 结构化数据
  • 用自然语言检索 Agent Ready 自身的方法论、检查项、规范与内容库
  • 提供扫描、结果解读与优先级修复计划等引导式流程
适用场景
适合让助手审计网站对 AI 智能体与爬虫的友好程度,或检查刚写好的 JSON-LD。面向站长、SEO 与开发团队,需要带评分的检查结果和具体修复指引,而非通用 SEO 或性能审计。
运行要求
可作为托管 Streamable HTTP 端点使用,也可通过 npm 包 agent-ready-mcp 在本地运行,需要 Node.js。匿名使用无需密钥;在 AGENT_READY_API_KEY 中提供 Pro 密钥可解锁更大扫描与扫描历史。另有可选变量覆盖 API 地址与超时。需要访问 agent-ready.dev 的网络连接。
安装前请注意
AGENT_READY_API_KEY 中的 Pro 密钥是账户的 bearer 凭据,勿放入共享配置。扫描内容会发送到托管的 agent-ready.dev 服务,扫描执行与存储均在该服务端完成。匿名使用限制为每 IP 每 30 天 3 次扫描、深度 25 页,扫描历史仅密钥所有者可见。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Agent Ready,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.mlava%2Fagent-ready-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "agent-ready": {
      "type": "http",
      "url": "https://agent-ready.dev/api/v1/mcp"
    }
  }
}

README

agent-ready-mcp

MCP server for Agent Ready — scan any URL for AI agent readability against the Vercel Agent Readability Spec, the llmstxt.org standard, and agent-protocol manifests (MCP server cards, A2A, agents.json, agent-permissions.json, UCP, x402, NLWeb). 72 checks across four spec families — 40 site and page checks (15 site-wide + 25 per-page), 10 against llmstxt.org, and 22 against agent-protocol manifests — each with per-check fix guidance, plus a separate accessibility sub-score from 23 WCAG 2.2 / layout-stability checks.

Hosted at https://agent-ready.dev/api/v1/mcp (Streamable HTTP); this package is a thin stdio wrapper around the same REST endpoints, distributed via npm for local MCP clients (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf).

Features

  • scan_site — fresh agent-readability scan on any URL. Works without a key on the anonymous free tier (3 scans/30 days per IP, 25-page depth, synchronous); with a Pro key it scans up to 250 pages, polling the hosted API up to 60s.
  • get_scan — fetch a previously-run scan by id (Pro key required — scan history is account-scoped).
  • ask — natural-language (NLWeb) search over Agent Ready's own methodology, checks, and specs. Public, no API key required; returns Schema.org-typed results.
  • validate_structured_data — validate a page's (or a pasted) JSON-LD against Agent Ready's structured-data checks. Public, no API key required; paste mode needs no network, so an agent can check JSON-LD it just authored.
  • Three discovery prompts — scan, interpret_scan, remediation_plan. End-to-end workflows from URL → score → fix-it plan.
  • SKILL.md — Claude Skill descriptor included under skills/agent-ready/ for activation routing.

Setup

No key is required to start: scan_site, ask, and validate_structured_data all work anonymously out of the box (scan_site on the free anonymous quota — 3 scans per 30 days per IP at 25-page depth). An Agent Ready Pro API key unlocks 50 scans/month, 250-page depth, scan history (get_scan), and weekly monitoring — sign up at agent-ready.dev and issue a key from the dashboard. The env block in the configs below is optional; omit it to run keyless.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "agent-ready": {      "command": "npx",      "args": ["-y", "agent-ready-mcp@latest"],      "env": {        "AGENT_READY_API_KEY": "ar_live_..."      }    }  }}

Claude Code

bash
claude mcp add agent-ready \  -e AGENT_READY_API_KEY=ar_live_... \  -- npx -y agent-ready-mcp@latest

Cursor / VS Code / Windsurf

.cursor/mcp.json, .vscode/mcp.json, or ~/.codeium/windsurf/mcp_config.json:

json
{  "mcpServers": {    "agent-ready": {      "command": "npx",      "args": ["-y", "agent-ready-mcp@latest"],      "env": {        "AGENT_READY_API_KEY": "ar_live_..."      }    }  }}

Environment variables

VariableRequiredDefaultPurpose
AGENT_READY_API_KEYNo—Pro Bearer token from the Agent Ready dashboard. Without it, scan_site uses the anonymous free tier and get_scan is unavailable.
AGENT_READY_API_URLNohttps://agent-ready.devOverride for self-hosted or staging deployments.
AGENT_READY_SCAN_TIMEOUT_MSNo60000How long scan_site polls before returning a running placeholder.
AGENT_READY_GET_TIMEOUT_MSNo5000Timeout for get_scan and per-poll fetches.

Tools

ToolInputsReturns
scan_siteurl (string, required), pageLimit (number, optional, max 2000 — capped by your plan; fixed at 25 keyless)Scan object: Vercel score 0–100, llms.txt sub-score 0–100, per-check findings with howToFix strings. Keyless runs use the anonymous free tier (3 scans/30 days per IP) and return synchronously; with a Pro key, returns { id, status: "running" } placeholder if the scan exceeds the poll deadline.
get_scanid (string, scan id from a prior scan_site call)Same scan object as scan_site, or not_found if the id is unknown or doesn't belong to the authenticated user. Pro key required.
askq (string, required), itemType (optional corpus filter), mode (optional, list or summarize)NLWeb /ask over Agent Ready's methodology, checks, and specs. Public — no API key required. Schema.org-typed result objects.
validate_structured_dataexactly one of url (string) or jsonld (string)D-series structured-data result: mode, url, per-check findings, and a summary verdict. Public — no API key required. Validates schema lint + agent-coherence the first-party validators don't.

Prompts

PromptArgsWhat it does
scanurlFresh scan + high-level summary (score, rating, top 3–5 failures, next step).
interpret_scanidPlain-English explanation of a previous scan's findings, grouped by category.
remediation_planid, optional focus ("seo" or "agents")Prioritised fix-it doc with Now/Next/Later buckets and per-fix check ids.

Example workflow

You: Use agent-ready to scan https://my-saas.comClaude: [calls scan_site] Your site scored 78/100 (Good) on the Vercel Agent        Readability Spec. The top 3 fixes: …You: Can you build me a remediation plan?Claude: [calls remediation_plan with the scan id] Here's the prioritised list…

Skill (Anthropic Claude Skills)

A SKILL.md lives at skills/agent-ready/SKILL.md inside the package. To use it in Claude Desktop / Claude Code, copy the skills/agent-ready/ directory into ~/.claude/skills/.

The skill describes when to activate (URL + readability-audit intent), which tool to pick, how to surface scan results without dumping raw JSON, and when to defer to other tools (general SEO, performance profiling, code editing).

How it works

This package is a thin stdio→HTTPS wrapper:

MCP client (stdio) ↔ agent-ready-mcp ↔ HTTPS ↔ agent-ready.dev/api/v1/scans

All scan execution, persistence, and Pro-tier quota enforcement happen on the hosted server. The npm package only translates between MCP JSON-RPC over stdio and the REST API.

If you'd rather use the hosted MCP server directly (Streamable HTTP transport, no local install), point your MCP client at https://agent-ready.dev/api/v1/mcp with Authorization: Bearer ar_live_....

Methodology

The 72 checks, their weights, and the score formula are documented at agent-ready.dev/methodology. Both manifest.json and server.json in this repo conform to the relevant registry schemas (Glama Marketplace v0.3 and MCP registry 2025-12-11 respectively).

Development

bash
npm installnpm run build       # → dist/mcp-server.mjsnpm testnpm run typecheck

Releasing

See RELEASE.md. It is the source of truth for version surfaces, local checks, tag pushing, the GitHub Actions release workflow, and the manual post-release steps.

License

MIT — see LICENSE.

来源:README.md,提交 ab4818b

工具

3

scan_site

Scan a site for AI agent readability

Runs the agent-ready.dev scanner against a URL and returns structured results: Vercel score, llmstxt.org score, and per-check findings with remediation hints. Scans may take up to ~60s; for larger scans the tool returns a scan id and asks you to poll with get_scan.

输入参数url必填pageLimit

get_scan

Get a previous scan by id

Fetches a completed or in-progress scan by its id. Only scans owned by the authenticated API key's user are returned.

输入参数id必填

ask

Ask Agent Ready in natural language

Natural-language search (NLWeb /ask) over Agent Ready's own content — scoring methodology, the check registry, the specs it validates, and the content library (explainers, comparisons, how-to guides, glossary). Returns Schema.org-typed result objects. Optional itemType narrows to a corpus type; mode 'summarize' adds an extractive summary.

输入参数q必填modeitemType

版本历史

1
  1. v0.7.7最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分