llms.txt Generator
REMOTE · WWW.LLMS-TXT-GENERATOR.DE
Create, validate and audit llms.txt, incl. the Lighthouse Agentic Browsing check.
Available components
Last scanned (21 minutes ago)
Scores higher than 98% of remote servers
Reachable. Last reached 17 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 Security83
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 1 Oct 26 −1
- 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 security
- Schema quality: pass → fail ▼ functional
- Tool “check_lighthouse_agentic_browsing” now declares an output schema ▲ functional
- Tool “check_published_llms_txt” now declares an output schema ▲ functional
- Tool “generate_llms_txt” now declares an output schema ▲ functional
- 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 functional
- “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 cosmetic
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 15 Sept 26 +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.
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 17 Oct 2026 · Probed https://www.llms-txt-generator.de/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.llms-txt-generator.de | CN=YR1,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | RSA 2048 | SHA256-RSA | 681449be286e1aa65f3c5565ef0d44e9877 |
| SANs: www.llms-txt-generator.de | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.llms-txt-generator.de. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| de. | present | 26755 | 8 | Verified |
| llms-txt-generator.de. | present | 45306 | 13 | Verified |
| www.llms-txt-generator.de. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://analytics.polymarkt.de; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://secure.gravatar.com https://placehold.co https://webmcp-tool.com; font-src 'self' data:; connect-src 'self' https://analytics.polymarkt.de; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.llms-txt-generator.de/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.llms-txt-generator.de/api/mcp | HTTPS enforced | 308 | https://www.llms-txt-generator.de/api/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 →
check_lighthouse_agentic_browsing Check Lighthouse "Agentic Browsing" rules ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text of the llms.txt file. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| note | string | – | – |
| passed | boolean | yes | – |
| reference | string | – | – |
No examples provided.
check_published_llms_txt Check a website's published llms.txt ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Domain or any URL of the website, e.g. "example.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| contentType | string | – | – |
| found | boolean | yes | – |
| lighthouse | object | – | Result of the three Lighthouse 13.3 "llms-txt" audit rules. |
| message | string | – | – |
| note | string | – | – |
| redirects | array | – | – |
| status | integer | yes | – |
| url | string | yes | – |
| validation | object | – | Format check against the llmstxt.org proposal. |
No examples provided.
generate_llms_txt Generate llms.txt for a website ~247
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.
| Name | Type | Req | Description |
|---|---|---|---|
| maxPages | integer | – | Upper limit of pages to read. Default 15. |
| url | string | yes | The website, as a bare domain or full URL, e.g. "example.com" or "https://www.example.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| excluded | array | yes | – |
| finalUrl | string | yes | – |
| lighthouse | object | yes | Result of the three Lighthouse 13.3 "llms-txt" audit rules. |
| limitReached | boolean | yes | true when the page limit stopped the crawl. |
| llmsText | string | yes | The complete llms.txt draft in Markdown. |
| maxPages | integer | – | – |
| note | string | – | – |
| pageCount | integer | yes | – |
| publishedFile | object | – | Status of the llms.txt currently published on the site. |
| siteName | string | – | – |
| validation | object | yes | Format check against the llmstxt.org proposal. |
| warnings | array | yes | – |
No examples provided.
validate_llms_txt Validate llms.txt content ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| lighthouse | object | yes | Result of the three Lighthouse 13.3 "llms-txt" audit rules. |
| note | string | – | – |
| validation | object | yes | Format check against the llmstxt.org proposal. |
No examples provided.
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.
remote · www.llms-txt-generator.de
claude mcp add --transport http de-llms-txt-generator-llms-txt 'https://www.llms-txt-generator.de/api/mcp'
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.