AgentReady for your agent
Can an agent actually use your website?
Start with the public surface. Get evidence, a concrete fix pack, and a way to check the original findings after your changes ship.
Connect directly
The public MCP has no account requirement. Add it in a supported client, then ask for a public URL audit.
claude mcp add --transport http agentready https://www.agentready.me/api/mcpUse the hosted MCP or downloadable skill. The unscoped npm package named agentready belongs to another project.
Observe
scan_url returns findings and Fix Pack v2. Keep that pack; a separate get_fix_pack call would scan again.
Implement
Use the evidence, review gates, and acceptance checks. Candidate file paths need confirmation in your repository.
Verify
verify_fixes compares stable finding IDs. A failed or missing phase cannot establish a resolved fix.
More focused questions?
Use the crawler-access checker, OpenAPI readiness audit, or A2A card validator. These provide bounded diagnostics; they do not execute private API actions or certify a complete customer journey.