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.
—
—
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The `agent-ready-mcp` skill’s required runtime path `scan_site` (and `get_scan`) ingests scraped free text from the user-supplied `url` at `agent-ready.dev`, which could include outsider-authored prompt-injection content from that target page.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The skill config runs remote code via npx (agent-ready-mcp@latest) which fetches the package published on npm (https://www.npmjs.com/package/agent-ready-mcp) at runtime, and the client can alternatively point directly at the hosted MCP endpoint (https://agent-ready.dev/api/v1/mcp) which is a runtime external service supplying MCP instructions — both are required runtime dependencies that deliver/execute external code or control agent behavior.