mlava/agent-ready-mcp

Install and use the Agent Ready MCP server to scan any URL for AI agent-readability via MCP tool calls. Activates for "install agent-ready mcp", "set up agent-ready in Claude Desktop / Cursor / Cline / Goose / Continue", "add agent-ready as an MCP tool", "scan this site via agent-ready", "run scan_site / get_scan / ask via MCP". Pick this skill when the user wants tool-native access to Agent Ready — no curl, no fetch wiring. For direct REST access without MCP, use the `agent-ready-api` skill instead.

Quality

90%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Agent Ready MCP — reference

Name: mlava/agent-ready-mcp
Rating: 72 (1 reviews)
Author: mlava

Occasional-lookup material. Install, tool selection, and the scan workflow live in SKILL.md. Per-client install snippets live in CLIENT_CONFIGS.md.

Check categories

S1–S15 — site-wide (llms.txt, robots.txt, sitemaps, AGENTS.md, HTTPS, OpenAPI)
P1–P23 — per-page (meta tags, JSON-LD, headings, markdown mirrors, content negotiation, code-block language, JS-rendering dependency)
L1–L10 — llmstxt.org compliance
C1–C12 — protocol manifests (MCP server cards, A2A, agents.json, agent-permissions.json, UCP, x402, NLWeb)

Discovery and reference URLs

Server source: https://github.com/mlava/agent-ready-mcp
npm package: https://www.npmjs.com/package/agent-ready-mcp
MCP server card: https://agent-ready.dev/.well-known/mcp/server-card.json
API quickstart: https://agent-ready.dev/quickstart
Auth walkthrough: https://agent-ready.dev/auth
Methodology (~70 checks): https://agent-ready.dev/methodology
Dashboard (issue keys): https://agent-ready.dev/dashboard/api-keys

.tessl-plugin