AIReady
REMOTE · AI-READY.MAGICTEAMS.AI
Scan and fix your site's AI discoverability: crawler access, llms.txt, JSON-LD. Free.
Available components
Last scanned (11 hours ago)
Scores higher than 82% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1594 tokens (~83/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_ai_readiness” rewrote its description, which is the text the model reads security
- Tool “crawler_policy_guide” rewrote its description, which is the text the model reads security
- Tool “llms_txt_draft” rewrote its description, which is the text the model reads security
- Tool “robots_txt_for_ai” rewrote its description, which is the text the model reads security
- Tool “schema_jsonld_sample” rewrote its description, which is the text the model reads security
- Prompt “ai_crawler_rules” was removed ▼ functional
- Prompt “audit_site” was removed ▼ functional
- Prompt “write_llms_txt” was removed ▼ functional
- Tool “check_ai_readiness” dropped its output schema ▼ functional
- Tool “crawler_policy_guide” dropped its output schema ▼ functional
- Tool “llms_txt_draft” dropped its output schema ▼ functional
- Tool “robots_txt_for_ai” dropped its output schema ▼ functional
- Tool “schema_jsonld_sample” dropped its output schema ▼ functional
- Schema quality: fail → pass ▲ functional
- The server no longer declares the “prompts” capability functional
- Schema quality: excellent → good functional
- MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
- MCP protocol version: 2026-07-28 → 2025-11-25 functional
- Server version: 1.1.0 → 2.0.0 functional
- New tool “add_competitors” functional
- New tool “add_prompts” functional
- New tool “ask_ai_engine” functional
- New tool “create_project” functional
- New tool “get_action_plan” functional
- New tool “get_citations” functional
- New tool “get_run_status” functional
- New tool “get_usage” functional
- New tool “get_visibility_report” functional
- New tool “list_projects” functional
- New tool “list_prompts” functional
- New tool “run_visibility_check” functional
- New tool “scan_project_site” functional
- New tool “suggest_prompts” functional
- “check_ai_readiness” reworded the description of “domain” cosmetic
- “llms_txt_draft” reworded the description of “business_name” cosmetic
- “llms_txt_draft” reworded the description of “contact_email” cosmetic
- “llms_txt_draft” reworded the description of “description” cosmetic
- “llms_txt_draft” reworded the description of “key_pages” cosmetic
- “robots_txt_for_ai” reworded the description of “content_signals” cosmetic
- “robots_txt_for_ai” reworded the description of “policy” cosmetic
- “robots_txt_for_ai” reworded the description of “sitemap_url” cosmetic
- “schema_jsonld_sample” reworded the description of “address” cosmetic
- “schema_jsonld_sample” reworded the description of “description” cosmetic
- “schema_jsonld_sample” reworded the description of “name” cosmetic
- “schema_jsonld_sample” reworded the description of “price” cosmetic
- “schema_jsonld_sample” reworded the description of “questions” cosmetic
- “schema_jsonld_sample” reworded the description of “telephone” cosmetic
- “schema_jsonld_sample” reworded the description of “type” cosmetic
- “schema_jsonld_sample” reworded the description of “url” cosmetic
- Tool “crawler_policy_guide” changed its title: Crawler policy guide → AI crawler policy guide cosmetic
- Tool “robots_txt_for_ai” changed its title: Generate robots.txt for AI → Generate robots.txt AI rules cosmetic
- Tool “schema_jsonld_sample” changed its title: Generate JSON-LD sample → Generate JSON-LD cosmetic
- 18 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_ai_readiness” rewrote its description, which is the text the model reads security
- Schema quality: 199 → 232 ▼ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “ai_crawler_rules” functional
- New prompt “audit_site” functional
- New prompt “write_llms_txt” functional
- Server version: 1.0.0 → 1.1.0 functional
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +4
- Tool “check_ai_readiness” rewrote its description, which is the text the model reads security
- Tool “crawler_policy_guide” rewrote its description, which is the text the model reads security
- Tool “llms_txt_draft” rewrote its description, which is the text the model reads security
- Tool “robots_txt_for_ai” rewrote its description, which is the text the model reads security
- Tool “schema_jsonld_sample” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 6% → 100% ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- “check_ai_readiness” reworded the description of “domain” cosmetic
- “llms_txt_draft” reworded the description of “business_name” cosmetic
- “llms_txt_draft” reworded the description of “contact_email” cosmetic
- “llms_txt_draft” reworded the description of “description” cosmetic
- “llms_txt_draft” reworded the description of “key_pages” cosmetic
- “robots_txt_for_ai” reworded the description of “content_signals” cosmetic
- “robots_txt_for_ai” reworded the description of “policy” cosmetic
- “robots_txt_for_ai” reworded the description of “sitemap_url” cosmetic
- “schema_jsonld_sample” reworded the description of “address” cosmetic
- “schema_jsonld_sample” reworded the description of “description” cosmetic
- “schema_jsonld_sample” reworded the description of “name” cosmetic
- “schema_jsonld_sample” reworded the description of “price” cosmetic
- “schema_jsonld_sample” reworded the description of “questions” cosmetic
- “schema_jsonld_sample” reworded the description of “telephone” cosmetic
- “schema_jsonld_sample” reworded the description of “type” cosmetic
- “schema_jsonld_sample” reworded the description of “url” cosmetic
- 6 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://ai-ready.magicteams.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=magicteams.ai | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1cfc66abd9f4152413363703f28b487f |
| SANs: magicteams.ai, ai-ready.magicteams.ai, *.ai-ready.magicteams.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ai-ready.magicteams.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| magicteams.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai-ready.magicteams.ai/mcp | Verified | 200 | |
| http (plaintext) | http://ai-ready.magicteams.ai/mcp | HTTPS enforced | 301 | https://ai-ready.magicteams.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_competitors Add competitors ~50
Add competitors to a project so reports rank the brand against them. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| competitors | array | yes | Competitors |
| project_id | string | yes | Project id |
No output schema declared.
No examples provided.
add_prompts Add prompts to track ~55
Add prompts (questions buyers ask AI assistants) to a project. Duplicates are skipped. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | Project id |
| prompts | array | yes | Prompts |
No output schema declared.
No examples provided.
ask_ai_engine Ask an AI engine (live) ~159
Run one prompt through a live AI engine (ChatGPT, Gemini, Perplexity, Copilot or Google AI Mode) from a country and return the full answer, the pages it cited and, if a brand is given, whether and where it was named. Costs one engine check from the workspace budget. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Optional brand to look for |
| competitors | array | – | Optional competitor names to rank against |
| country | string | – | Two-letter country code (default US) |
| domain | string | – | Optional brand domain, to detect citations of its site |
| engine | string | – | Engine |
| prompt | string | yes | The question exactly as a buyer would type it |
No output schema declared.
No examples provided.
check_ai_readiness Check AI readiness ~109
Scan one website for AI discoverability: which AI crawlers robots.txt allows or blocks (OAI-SearchBot, ClaudeBot, PerplexityBot...), llms.txt, sitemap, schema.org data, meta tags and Content Signals. Returns a 0-100 score, grade and prioritized fixes. Fetches only the domain's /robots.txt, /llms.txt, /sitemap.xml and homepage.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain or URL, e.g. example.com |
No output schema declared.
No examples provided.
crawler_policy_guide AI crawler policy guide ~55
Reference table of AI crawlers and control tokens (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended...): owner, purpose and whether each drives AI citations or only training.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_project Start tracking a brand ~183
Create a project that tracks one brand's visibility in AI answers. Optionally add competitors and prompts in the same call. Use suggest_prompts first if you don't have prompts. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | – | Other spellings of the brand |
| brand | string | yes | Brand name as people write it |
| competitors | array | – | Competitors |
| countries | array | – | Two-letter country codes to ask from (default US) |
| description | string | – | What the business does and for whom (helps prompt suggestions) |
| domain | string | – | Brand website domain |
| engines | array | – | Engines to track (default all): chatgpt, gemini, perplexity, copilot, ai_mode |
| prompts | array | – | Prompts to track |
| schedule | string | – | How often to re-check |
No output schema declared.
No examples provided.
get_action_plan Get the action plan ~70
Prioritized steps to get named more often: dead cited pages to redirect, readiness fixes, prompts the brand loses and what to publish for each, sites to get listed on, and competitors to close the gap with. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | Project id |
No output schema declared.
No examples provided.
get_citations Get cited sources ~78
Which domains and pages AI engines cite for the project's prompts, which are the brand's own or a competitor's, and any of the brand's cited pages that now return 404. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window in days (default 30) |
| project_id | string | yes | Project id |
No output schema declared.
No examples provided.
get_run_status Get run status ~35
Progress and summary of a visibility run. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | Run id |
No output schema declared.
No examples provided.
get_usage Get usage and budget ~36
This month's engine spend, checks run and remaining budget, plus the price per check of each engine. (Requires an AIReady API key.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_visibility_report Get visibility report ~85
The brand's AI visibility: score, mention and citation rates, average rank, share of voice vs competitors, results per engine, country and prompt, trend over runs, sentiment, and untracked brands the engines recommend. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window in days (default 30) |
| project_id | string | yes | Project id |
No output schema declared.
No examples provided.
list_projects List tracked brands ~31
List the workspace's tracked brands (projects) with their latest visibility summary. (Requires an AIReady API key.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_prompts List a project's prompts ~33
The prompts a project tracks. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | Project id |
No output schema declared.
No examples provided.
llms_txt_draft Draft llms.txt ~87
Draft a starter llms.txt from a business name, one-line summary, key pages and contact, so AI assistants get a curated map of the site.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | Business or site name |
| contact_email | string | – | Contact email |
| description | string | yes | One sentence about what you offer |
| key_pages | array | – | Key pages |
No output schema declared.
No examples provided.
robots_txt_for_ai Generate robots.txt AI rules ~81
Generate robots.txt rules for an AI policy: max_visibility, search_only, block_training or block_all_ai, optionally with Content-Signal lines and a sitemap reference.
| Name | Type | Req | Description |
|---|---|---|---|
| content_signals | boolean | – | Add Content-Signal lines (default true) |
| policy | string | yes | AI crawler policy |
| sitemap_url | string | – | Optional sitemap URL |
No output schema declared.
No examples provided.
run_visibility_check Run a visibility check ~75
Run every active prompt of a project through every tracked engine and country. Starts immediately and finishes in the background (usually 1-5 minutes); poll get_run_status. Spends engine checks from the monthly budget; the estimate is returned. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | Project id |
No output schema declared.
No examples provided.
scan_project_site Scan the project's site ~45
Run the AI readiness scan on the project's own domain and save it to the project history. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | Project id |
No output schema declared.
No examples provided.
schema_jsonld_sample Generate JSON-LD ~121
Generate a schema.org JSON-LD snippet (organization, local_business, product or faq) to paste into a page head so AI systems identify the entity correctly.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address (local_business) |
| description | string | – | Short description |
| name | string | yes | Entity name |
| price | string | – | Price (product) |
| questions | array | – | FAQ items (faq) |
| telephone | string | – | Phone (local_business) |
| type | string | yes | Schema type |
| url | string | yes | Site URL |
No output schema declared.
No examples provided.
suggest_prompts Suggest buyer prompts ~78
Suggest the questions real buyers ask AI assistants in this brand's category (category, problem, comparison and branded prompts). Does not save them; pass the ones you want to add_prompts. (Requires an AIReady API key.)
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many (default 15) |
| project_id | string | yes | Project id |
No output schema declared.
No examples provided.
How do I install the AIReady MCP server?
AIReady is a hosted endpoint at https://ai-ready.magicteams.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ai-ready.magicteams.ai
claude mcp add --transport http everyai-com-ai-ready 'https://ai-ready.magicteams.ai/mcp'
What is the AIReady MCP server?
AIReady is an MCP server listed in the public MCP registry as io.github.everyai-com/ai-ready. Scan and fix your site's AI discoverability: crawler access, llms.txt, JSON-LD. Free. This page covers its hosted endpoint (https://ai-ready.magicteams.ai/mcp).
Is the AIReady MCP server safe to use?
AIReady scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AIReady MCP server expose?
AIReady exposes 19 tools: check_ai_readiness, crawler_policy_guide, robots_txt_for_ai, llms_txt_draft, schema_jsonld_sample, and 14 more. Their descriptions and schemas cost roughly 1,466 tokens of context every time the server is loaded.
Does the AIReady MCP server require authentication?
No. We connected to AIReady without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AIReady MCP server still maintained?
AIReady is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.