# llms.txt Generator (remote · www.llms-txt-generator.de)

Create, validate and audit llms.txt, incl. the Lighthouse Agentic Browsing check.

- Trust score: 90/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `www.llms-txt-generator.de`: 90/100 (this document), [markdown](https://verifymcp.io/servers/de-llms-txt-generator-llms-txt/api-mcp.md), [page](https://verifymcp.io/servers/de-llms-txt-generator-llms-txt/api-mcp)

## Channel facts

- Endpoint: `https://www.llms-txt-generator.de/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-10-17.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 748 tokens (~187/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 llms.txt Generator MCP server?

llms.txt Generator is a hosted endpoint at https://www.llms-txt-generator.de/api/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 de-llms-txt-generator-llms-txt 'https://www.llms-txt-generator.de/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "de-llms-txt-generator-llms-txt": {
      "url": "https://www.llms-txt-generator.de/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "de-llms-txt-generator-llms-txt": {
      "type": "http",
      "url": "https://www.llms-txt-generator.de/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.de-llms-txt-generator-llms-txt]
url = "https://www.llms-txt-generator.de/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-llms-txt-generator-llms-txt": {
      "type": "remote",
      "url": "https://www.llms-txt-generator.de/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add de-llms-txt-generator-llms-txt --url 'https://www.llms-txt-generator.de/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  de-llms-txt-generator-llms-txt:
    url: "https://www.llms-txt-generator.de/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "de-llms-txt-generator-llms-txt": {
      "Transport": "http",
      "Url": "https://www.llms-txt-generator.de/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add de-llms-txt-generator-llms-txt -t streamable-http -u 'https://www.llms-txt-generator.de/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "de-llms-txt-generator-llms-txt": {
      "type": "http",
      "url": "https://www.llms-txt-generator.de/api/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-10-01 (score 90, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_lighthouse_agentic_browsing” rewrote its description, which is the text the model reads
- [security] Tool “check_published_llms_txt” rewrote its description, which is the text the model reads
- [security] Tool “generate_llms_txt” rewrote its description, which is the text the model reads
- [security] Tool “validate_llms_txt” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool “check_lighthouse_agentic_browsing” now declares an output schema
- [functional improvement] Tool “check_published_llms_txt” now declares an output schema
- [functional improvement] Tool “generate_llms_txt” now declares an output schema
- [functional improvement] Tool “validate_llms_txt” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Server version: 1.0.0 → 1.1.0
- [cosmetic] “check_lighthouse_agentic_browsing” reworded the description of “content”
- [cosmetic] “check_published_llms_txt” reworded the description of “url”
- [cosmetic] “generate_llms_txt” reworded the description of “maxPages”
- [cosmetic] “generate_llms_txt” reworded the description of “url”
- [cosmetic] “validate_llms_txt” reworded the description of “content”
- [cosmetic] “validate_llms_txt” reworded the description of “expectedHostname”
- [cosmetic] Tool “check_lighthouse_agentic_browsing” changed its title: Lighthouse-Audit "Agentic Browsing" prüfen → Check Lighthouse "Agentic Browsing" rules
- [cosmetic] Tool “check_published_llms_txt” changed its title: Veröffentlichte llms.txt prüfen → Check a website's published llms.txt
- [cosmetic] Tool “generate_llms_txt” changed its title: llms.txt erzeugen → Generate llms.txt for a website
- [cosmetic] Tool “validate_llms_txt” changed its title: llms.txt validieren → Validate llms.txt content

### 2026-09-28 (score 91, +7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 84, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `generate_llms_txt` (~247 tokens)

Generate llms.txt for a website

Use this when the user wants a new llms.txt file for a public website they name. Reads up to 15 public HTML pages of that one domain (start page, XML sitemap, internal links) and returns a ready-to-publish llms.txt draft in Markdown, plus a format validation score, the Lighthouse "Agentic Browsing" result, the status of any llms.txt already published on the site, and the URLs that were left out with the reason. Deterministic: no language model is involved, every title and description is taken from the pages themselves. Limitations: honors robots.txt and stops if the start page is disallowed; does not render JavaScript, does not log in, and does not follow links to other domains; one request can take up to about a minute. Do not use this to fetch arbitrary page content or for sites the user only mentions in passing. Result messages are in German.

Input parameters:

- `maxPages` (integer): Upper limit of pages to read. Default 15.
- `url` (string, required): The website, as a bare domain or full URL, e.g. "example.com" or "https://www.example.com".

Output parameters:

- `excluded` (array)
- `finalUrl` (string)
- `lighthouse` (object): Result of the three Lighthouse 13.3 "llms-txt" audit rules.
- `limitReached` (boolean): true when the page limit stopped the crawl.
- `llmsText` (string): The complete llms.txt draft in Markdown.
- `maxPages` (integer)
- `note` (string)
- `pageCount` (integer)
- `publishedFile` (object): Status of the llms.txt currently published on the site.
- `siteName` (string)
- `validation` (object): Format check against the llmstxt.org proposal.
- `warnings` (array)

### `validate_llms_txt` (~167 tokens)

Validate llms.txt content

Use this when the user pastes the text of an llms.txt file and wants it checked or improved. Checks the text against the llmstxt.org format proposal: H1 title, summary blockquote, H2 sections, absolute Markdown links, duplicates, links to other domains, file size and update date. Returns a 0-100 score, findings with severity and line number, and the Lighthouse "Agentic Browsing" result. Works only on the text provided; it does not fetch anything from the internet. Finding messages are in German.

Input parameters:

- `content` (string, required): The full text of the llms.txt file.
- `expectedHostname` (string): Optional hostname of the website, e.g. "www.example.com". Enables the warning for links to other domains.

Output parameters:

- `lighthouse` (object): Result of the three Lighthouse 13.3 "llms-txt" audit rules.
- `note` (string)
- `validation` (object): Format check against the llmstxt.org proposal.

### `check_published_llms_txt` (~120 tokens)

Check a website's published llms.txt

Use this when the user asks whether a website already has an llms.txt, whether it is served correctly, or why PageSpeed Insights / Lighthouse flags it. Requests exactly one URL, https://<domain>/llms.txt, and reports HTTP status, content type, redirects, the file content, the format validation and the Lighthouse result. Does not crawl other pages and does not change anything on the site. Messages are in German.

Input parameters:

- `url` (string, required): Domain or any URL of the website, e.g. "example.com".

Output parameters:

- `content` (string)
- `contentType` (string)
- `found` (boolean)
- `lighthouse` (object): Result of the three Lighthouse 13.3 "llms-txt" audit rules.
- `message` (string)
- `note` (string)
- `redirects` (array)
- `status` (integer)
- `url` (string)
- `validation` (object): Format check against the llmstxt.org proposal.

### `check_lighthouse_agentic_browsing` (~120 tokens)

Check Lighthouse "Agentic Browsing" rules

Use this when the user only wants to know whether a given llms.txt text passes the Lighthouse 13.3 "Agentic Browsing" audit (llms-txt). Applies exactly its three rules: an H1 exists, at least one Markdown link, more than 50 characters. On failure it returns Lighthouse's original message. Works only on the text provided and does not fetch anything. For a full format check use validate_llms_txt.

Input parameters:

- `content` (string, required): The text of the llms.txt file.

Output parameters:

- `checks` (array)
- `note` (string)
- `passed` (boolean)
- `reference` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/de-llms-txt-generator-llms-txt/api-mcp#diagnostics

## Score history

- 2026-10-17: 90
- 2026-10-16: 90
- 2026-10-15: 90
- 2026-10-14: 90
- 2026-10-13: 90
- 2026-10-12: 90
- 2026-10-10: 90
- 2026-10-04: 90
- 2026-10-03: 90
- 2026-10-02: 90
- 2026-10-01: 90
- 2026-09-30: 91
- 2026-09-29: 91
- 2026-09-28: 91
- 2026-09-27: 84
- 2026-09-26: 84
- 2026-09-25: 84
- 2026-09-24: 84
- 2026-09-23: 83
- 2026-09-22: 83
- 2026-09-21: 82
- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78

## Common questions

### What is the llms.txt Generator MCP server?

llms.txt Generator is an MCP server listed in the public MCP registry as de.llms-txt-generator/llms-txt. Create, validate and audit llms.txt, incl. the Lighthouse Agentic Browsing check. This page covers its hosted endpoint (https://www.llms-txt-generator.de/api/mcp).

### Is the llms.txt Generator MCP server safe to use?

llms.txt Generator scores 90 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 llms.txt Generator MCP server expose?

llms.txt Generator exposes 4 tools: generate_llms_txt, validate_llms_txt, check_published_llms_txt, check_lighthouse_agentic_browsing. Their descriptions and schemas cost roughly 654 tokens of context every time the server is loaded.

### Does the llms.txt Generator MCP server require authentication?

No. We connected to llms.txt Generator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the llms.txt Generator MCP server still maintained?

llms.txt Generator is still listed as active in the MCP registry. We last reached this channel on 17 October 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://www.llms-txt-generator.de/api/mcp
- Website: https://www.llms-txt-generator.de/
- Changelog RSS feed: https://verifymcp.io/servers/de-llms-txt-generator-llms-txt/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/de-llms-txt-generator-llms-txt/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/de-llms-txt-generator-llms-txt/api-mcp