Skip to content

llms.txt Generator MCP server

de.llms-txt-generator/llms-txtllms-txt-generator.destreamable-httpv1.0.0Scanned

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

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 2
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the llms.txt Generator MCP server can do

The llms.txt Generator MCP server is published by llms-txt-generator.de, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: generate_llms_txt, check_published_llms_txt and check_lighthouse_agentic_browsing), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (generate_llms_txt and check_published_llms_txt); 2 tools can send data out of your system (generate_llms_txt and check_published_llms_txt).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • check_lighthouse_agentic_browsingUse this when the user only wants to know whether a given llms.txt text passes the Lighthouse 13.3 "Agentic Browsing" audit (llms-txt).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check Lighthouse "Agentic Browsing" rules
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_published_llms_txtUse 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.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a website's published llms.txt
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • generate_llms_txtUse this when the user wants a new llms.txt file for a public website they name.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "generate_llms_txt" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "generate_llms_txt" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "generate_llms_txt" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Generate llms.txt for a website
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • validate_llms_txtUse this when the user pastes the text of an llms.txt file and wants it checked or improved.No findings

    Why it is in this group

    • The name "validate_llms_txt" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Validate llms.txt content
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:51 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.llms-txt-generator.de/api/mcp: tools/list returned 4 tools to an anonymous client, including generate_llms_txt (write), check_published_llms_txt (write), check_lighthouse_agentic_browsing (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "generate_llms_txt" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "generate_llms_txt" says "generate": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http llms-txt https://www.llms-txt-generator.de/api/mcp
claude mcp add --transport http llms-txt https://www.llms-txt-generator.de/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__llms-txt__validate_llms_txt"
    ],
    "ask": [
      "mcp__llms-txt__generate_llms_txt",
      "mcp__llms-txt__check_published_llms_txt",
      "mcp__llms-txt__check_lighthouse_agentic_browsing"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as llms-txt. Review it before you use it.

Capability tags behind 2 rules
  • mcp__llms-txt__generate_llms_txt untrusted-input, outbound
  • mcp__llms-txt__check_published_llms_txt untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/de.llms-txt-generator/llms-txt/verify?hash=208cebd51813b5ba23761405f97643584d17e73f7159ea92e8cf193d26069968" | jq -e '.changed == false'

Pinned hash 208cebd51813, from Nov 14, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/de.llms-txt-generator/llms-txt/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for de.llms-txt-generator/llms-txt
[![Anlyon Radar](https://radar.anlyon.com/badge/de.llms-txt-generator/llms-txt.svg)](https://radar.anlyon.com/servers/de.llms-txt-generator/llms-txt)

Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.

llms.txt Generator MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the llms.txt Generator MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the llms.txt Generator MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the llms.txt Generator MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the llms.txt Generator MCP server have?

4 tools: 3 write, 1 read. generate_llms_txt, check_published_llms_txt, check_lighthouse_agentic_browsing and validate_llms_txt.

Does the llms.txt Generator MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the llms.txt Generator MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): generate_llms_txt and check_published_llms_txt.

Has the llms.txt Generator MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.