AIReady MCP Server

by everyai-com Your server? Claim it

answering

AIReady is answering right now. Last checked 9 min ago. It exposes 5 tools. Last commit 2 Oct 2026.

Scan and fix your site's AI discoverability: crawler access, llms.txt, JSON-LD. Free.

Uptime history 8 days of history · worst day 99%

8 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

116 ms

Response time

average over 24h

Stars

last commit 2 Oct 2026

What changed 17

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 6 October 2026. No other catalogue keeps this.

10 Oct 5 tool descriptions were rewritten check_ai_readiness, crawler_policy_guide, llms_txt_draft and 2 more

10 Oct 4 tools changed the parameters they ask for check_ai_readiness, llms_txt_draft, robots_txt_for_ai and 1 more

6 Oct 5 tool descriptions were rewritten check_ai_readiness, crawler_policy_guide, llms_txt_draft and 2 more

6 Oct 3 tools changed the parameters they ask for llms_txt_draft, robots_txt_for_ai, schema_jsonld_sample

AIReady missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add ai-ready --transport http https://ai-ready.magicteams.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "ai-ready": {
      "url": "https://ai-ready.magicteams.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.ai-ready]
url = "https://ai-ready.magicteams.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "ai-ready": {
      "url": "https://ai-ready.magicteams.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "ai-ready": {
      "url": "https://ai-ready.magicteams.ai/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

crawler

crawler_policy_guide

Static reference of 13 known AI crawlers and control tokens (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended...): owner, purpose, whether each drives AI citations or training, plus rules of thumb. Use to decide which bots to allow or block. No site is fetched. Do NOT use to audit a real site (use check_ai_readiness) or to produce rules (use robots_txt_for_ai).

llms

llms_txt_draft

Draft a starter llms.txt (Markdown: # name, > one-line summary, key page links, contact) from business details, to publish at the site root so AI agents get a curated summary. Use when a site has no llms.txt. Do NOT use for crawler access rules (use robots_txt_for_ai) or schema.org markup (use schema_jsonld_sample).

readiness

check_ai_readiness

Live scan of one domain's AI discoverability: fetches its /robots.txt, /llms.txt, /sitemap.xml and homepage, then returns a 0-100 score, grade, per-crawler allow/block status and prioritized fixes. Use to audit a real site. Do NOT use for general advice on which bots to allow (use crawler_policy_guide) or to write new rules (use robots_txt_for_ai).

robots

robots_txt_for_ai

Generate robots.txt User-agent rules for all known AI crawlers from a chosen policy (max_visibility, search_only, block_training, block_all_ai), with optional Content-Signal and Sitemap lines, to paste into an existing robots.txt. Use when writing AI crawler rules. Do NOT use to check a live site's current rules (use check_ai_readiness) or for bot background (use crawler_policy_guide).

schema

schema_jsonld_sample

Generate a schema.org JSON-LD snippet (Organization, LocalBusiness, Product with Offer, or FAQPage) from your details, with placement tips, so search engines and AI assistants can identify the entity. Use when adding structured data to a page. Do NOT use to check whether a site already has structured data (use check_ai_readiness) or for llms.txt (use llms_txt_draft).

Endpoints

URL	Transport	State	Latency	Checked
https://ai-ready.magicteams.ai/mcp	streamable-http	answering	65 ms	9 min ago

Alternatives to AIReady

same job, measured the same way

AI Visibility Audit — Can AI crawlers read and cite your site?

by rowb-ai-visibility

One-call audit: robots.txt AI-bot rules, llms.txt, JSON-LD, meta tags, sitemap. Score plus fixes.

1 tools answering

Geolint

by iliasabk

ESLint for AI search: audits AI-crawler access, llms.txt, schema and citability.

62 installs/wk local only

Alice

by tranx

Audit any site's AI visibility from your assistant: crawler access, rendering, and schema.

2 tools answering

AI Search Kit

by modernmustardseed

Audits AI-crawler access, structured data and llms.txt on a site, and drafts the fixes.

5 tools answering

llms.txt Checker - AI Readiness Audit

by apifymcpfactory-droid

Checks llms.txt, AI crawler access in robots.txt, and sitemap - with a 0-100 AI readiness score.

answering

GEO Inspector

by bigsupe55

Inspect a site's AI-search readiness: AI crawler access, llms.txt, schema markup, meta directives

34 installs/wk local only

agentbuilt

by agentbuilt

Free AI-readiness audit of any URL: AI crawler rules, JS-free text, JSON-LD, llms.txt. Tool catalog.

3 tools answering

MaxAEO AI Visibility MCP

by maxaeo

Local-first MCP server for AI visibility, GEO/AEO, llms.txt, and AI crawler readiness audits.

49 installs/wk local only

AIReady — questions

Answers built from our own checks of this server.

What can AIReady do?

It exposes 5 tools, read directly from the server on our last check. Among them: check_ai_readiness, crawler_policy_guide, llms_txt_draft, robots_txt_for_ai, schema_jsonld_sample. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is AIReady working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 116 ms. The bar chart above shows every period we have measured.

How do I connect AIReady?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does AIReady need an API key?

No. AIReady completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is AIReady?

It answers our handshake in 116 ms on average, which is faster than 79% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is AIReady open source?

Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.