# LLMready (remote · answer-engine-ready.lovable.app)

Audit websites for AI search readiness and generate or validate llms.txt. Free quick check.

- Trust score: 82/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `answer-engine-ready.lovable.app`: 82/100 (this document), [markdown](https://verifymcp.io/servers/app-lovable-answer-engine-ready-llmready/answer-engine-ready.md), [page](https://verifymcp.io/servers/app-lovable-answer-engine-ready-llmready/answer-engine-ready)

## Channel facts

- Endpoint: `https://answer-engine-ready.lovable.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 790 tokens (~112/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http app-lovable-answer-engine-ready-llmready 'https://answer-engine-ready.lovable.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-lovable-answer-engine-ready-llmready": {
      "url": "https://answer-engine-ready.lovable.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-lovable-answer-engine-ready-llmready": {
      "type": "http",
      "url": "https://answer-engine-ready.lovable.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-lovable-answer-engine-ready-llmready]
url = "https://answer-engine-ready.lovable.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-lovable-answer-engine-ready-llmready": {
      "type": "remote",
      "url": "https://answer-engine-ready.lovable.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-lovable-answer-engine-ready-llmready --url 'https://answer-engine-ready.lovable.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-lovable-answer-engine-ready-llmready:
    url: "https://answer-engine-ready.lovable.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-lovable-answer-engine-ready-llmready": {
      "Transport": "http",
      "Url": "https://answer-engine-ready.lovable.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-lovable-answer-engine-ready-llmready -t streamable-http -u 'https://answer-engine-ready.lovable.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-lovable-answer-engine-ready-llmready": {
      "type": "http",
      "url": "https://answer-engine-ready.lovable.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, +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.

### 2026-11-01 (score 81, +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.

### 2026-10-31 (score 80, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 80)

First indexed and scored.

## MCP tools (7)

### `quick_check` (~128 tokens)

Quick AI search readiness check (free)

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.

Input parameters:

- `url` (string, required): Website URL or bare domain, e.g. https://example.com or example.com

### `audit_url` (~96 tokens)

Audit a website for AI search readiness

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.

Input parameters:

- `url` (string, required): Website URL or bare domain, e.g. https://example.com or example.com

### `get_audit` (~65 tokens)

Get a saved audit

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.

Input parameters:

- `id` (string, required): Audit id returned by audit_url or list_audits

### `list_audits` (~74 tokens)

List your audits

List audits saved on your LLMready account, newest first, optionally for one domain. No credit cost. Requires signing in with LLMready Pro.

Input parameters:

- `domain` (string): Only audits for this domain, e.g. example.com
- `limit` (integer): How many to return (default 20)

### `generate_llms_txt` (~73 tokens)

Generate llms.txt and llms-full.txt

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.

Input parameters:

- `url` (string, required): Website URL or bare domain

### `validate_llms_txt` (~99 tokens)

Validate an llms.txt file

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.

Input parameters:

- `content` (string): Raw llms.txt content
- `url` (string): Site URL whose live /llms.txt should be fetched and validated

### `get_usage` (~35 tokens)

Check API credits

Show how many LLMready credits are used and left this month. No credit cost. Requires signing in with LLMready Pro.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-lovable-answer-engine-ready-llmready/answer-engine-ready#diagnostics

## Score history

- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80

## Common questions

### 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.

## Links

- Remote endpoint: https://answer-engine-ready.lovable.app/mcp
- Website: https://answer-engine-ready.lovable.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-lovable-answer-engine-ready-llmready/answer-engine-ready.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-lovable-answer-engine-ready-llmready/answer-engine-ready.json
- HTML version of this page: https://verifymcp.io/servers/app-lovable-answer-engine-ready-llmready/answer-engine-ready