
LLMready MCP server
Which MCP servers are LLMready's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-30
- Registry nameapp.lovable.answer-engine-ready/llmreadyverified in the MCP registry
The registry name sits under answer-engine-ready.lovable.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-30
- Tools7
- Server calls itselfllmready
- Server version1.2.0
- Protocol version2025-06-18
On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 2062 ms.
- Its tools do every use case we checked: generate and validate an llms.txt file; score site content extractability and metadata.
- Checked on 3 of the 7 days it takes to judge reliability.
Once connected
- For "generate and validate an llms.txt file", the likely first call is generate_llms_txt.
- For "score site content extractability and metadata", the likely first call is audit_url.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- What an agent can do with it2 of 2 use cases
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer1648 ms
- Space in an agent's context≈ 985 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · check whether AI crawlers can access robots.txt rules
- can do · generate and validate an llms.txt file
- can do · score site content extractability and metadata
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
quick_checkFree, no sign-in, Pro or credits needed: 10 checks a minute and 100 a day per IP address (per account when signed in). Checks a public website live and returns its 0–100 AI search readiness score, grade, category scores, which AI crawlers…
audit_urlCrawl a public website live and score how well AI search engines (ChatGPT Search, Perplexity, Gemini, Claude) can access and read it: 0–100 score, grade, category scores, prioritized fixes and a shareable report link. Costs 1 credit…
get_auditFetch a saved audit from your LLMready account by id, including score, failing checks, AI crawler access and fixes. No credit cost. Requires signing in with LLMready Pro.
list_auditsList audits saved on your LLMready account, newest first, optionally for one domain. No credit cost. Requires signing in with LLMready Pro.
generate_llms_txtCrawl a website's key pages and generate a spec-compliant /llms.txt plus an /llms-full.txt with page content as Markdown, ready to upload to the site root. Costs 1 credit. Requires signing in with LLMready Pro.
validate_llms_txtCheck llms.txt content against the llmstxt.org proposal and list errors and warnings by line. Pass `content` to check text, or `url` to fetch and check a site's live /llms.txt. No credit cost. Requires signing in with LLMready Pro.
get_usageShow how many LLMready credits are used and left this month. No credit cost. Requires signing in with LLMready Pro.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"llmready": {
"type": "http",
"url": "https://answer-engine-ready.lovable.app/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http answer-engine-ready https://answer-engine-ready.lovable.app/mcpclaude.ai, ChatGPT and other clients: add https://answer-engine-ready.lovable.app/mcp as a custom connector in the settings.
OpenAPI spec
7 paths, read 2026-10-30. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.