LLMready
REMOTE · ANSWER-ENGINE-READY.LOVABLE.APP
Audit websites for AI search readiness and generate or validate llms.txt. Free quick check.
Available components
Last scanned (22 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 4 Nov 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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 790 tokens (~112/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 80
First indexed and scored.
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 4 Nov 2026 · Probed https://answer-engine-ready.lovable.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lovable.app | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a0305f14b2a99af130a9e43af07d3e5 |
| SANs: lovable.app, *.lovable.app | ||||||
| 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 answer-engine-ready.lovable.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| lovable.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://answer-engine-ready.lovable.app/.well-known/oauth-protected-resource"
Bearer realm="mcp", resource_metadata="https://answer-engine-ready.lovable.app/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://answer-engine-ready.lovable.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://answer-engine-ready.lovable.app/mcp |
| Authorisation server | https://jngyinpsjkdrhylnidnd.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://answer-engine-ready.lovable.app/mcp | Verified | 200 | |
| http (plaintext) | http://answer-engine-ready.lovable.app/mcp | HTTPS enforced | 301 | https://answer-engine-ready.lovable.app/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 →
audit_url Audit a website for AI search readiness ~96
Crawl 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. Requires signing in with LLMready Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL or bare domain, e.g. https://example.com or example.com |
No output schema declared.
No examples provided.
generate_llms_txt Generate llms.txt and llms-full.txt ~73
Crawl 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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL or bare domain |
No output schema declared.
No examples provided.
get_audit Get a saved audit ~65
Fetch 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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Audit id returned by audit_url or list_audits |
No output schema declared.
No examples provided.
get_usage Check API credits ~35
Show how many LLMready credits are used and left this month. No credit cost. Requires signing in with LLMready Pro.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_audits List your audits ~74
List audits saved on your LLMready account, newest first, optionally for one domain. No credit cost. Requires signing in with LLMready Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Only audits for this domain, e.g. example.com |
| limit | integer | – | How many to return (default 20) |
No output schema declared.
No examples provided.
quick_check Quick AI search readiness check (free) ~128
Free, 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 robots.txt allows or blocks, whether llms.txt exists, and the top 3 fixes. Saves no report — audit_url (Pro) lists every failing check with a shareable report and badge.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL or bare domain, e.g. https://example.com or example.com |
No output schema declared.
No examples provided.
validate_llms_txt Validate an llms.txt file ~99
Check 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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Raw llms.txt content |
| url | string | – | Site URL whose live /llms.txt should be fetched and validated |
No output schema declared.
No examples provided.
How do I install the LLMready MCP server?
LLMready is a hosted endpoint at https://answer-engine-ready.lovable.app/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 · answer-engine-ready.lovable.app
claude mcp add --transport http app-lovable-answer-engine-ready-llmready 'https://answer-engine-ready.lovable.app/mcp'
What is the LLMready MCP server?
LLMready is an MCP server listed in the public MCP registry as app.lovable.answer-engine-ready/llmready. Audit websites for AI search readiness and generate or validate llms.txt. Free quick check. This page covers its hosted endpoint (https://answer-engine-ready.lovable.app/mcp).
Is the LLMready MCP server safe to use?
LLMready scores 82 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 LLMready MCP server expose?
LLMready exposes 7 tools: quick_check, audit_url, get_audit, list_audits, generate_llms_txt, and 2 more. Their descriptions and schemas cost roughly 570 tokens of context every time the server is loaded.
Does the LLMready MCP server require authentication?
Yes. LLMready asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the LLMready MCP server still maintained?
LLMready is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.