CtrlK
BlogDocsLog inGet started
Tessl Logo

mlava/agent-ready-mcp

Install and use the Agent Ready (agent-ready.dev) 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

—

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

REFERENCE.md

Agent Ready MCP — reference

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–C21 — protocol manifests (MCP server cards, A2A, agents.json, agent-permissions.json, UCP, x402, NLWeb, API Catalog, Web Bot Auth, Agent Skills Discovery, A2UI, MPP, AP2, ACP)
  • A1–A23 — accessibility (WCAG 2.2 / layout stability), scored as a separate accessibility sub-score. Checks with nothing to grade are marked not-applicable and excluded from that sub-score

Discovery and reference URLs

CLIENT_CONFIGS.md

REFERENCE.md

SKILL.md

tile.json