llms.txt for agents
REMOTE · LLMSTXTMCP.DEV · SCANNED SEP 24
Any site's llms.txt: find the covering index, read its linked docs as markdown, search sections.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the llms.txt for agents MCP server?
llms.txt for agents is a hosted endpoint at https://llmstxtmcp.dev/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 · llmstxtmcp.dev
claude mcp add --transport http ux-xd-llms-txt 'https://llmstxtmcp.dev/mcp'
{
"mcpServers": {
"ux-xd-llms-txt": {
"url": "https://llmstxtmcp.dev/mcp"
}
}
} {
"servers": {
"ux-xd-llms-txt": {
"type": "http",
"url": "https://llmstxtmcp.dev/mcp"
}
}
} [mcp_servers.ux-xd-llms-txt] url = "https://llmstxtmcp.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ux-xd-llms-txt": {
"type": "remote",
"url": "https://llmstxtmcp.dev/mcp",
"enabled": true
}
}
} openclaw mcp add ux-xd-llms-txt --url 'https://llmstxtmcp.dev/mcp' --transport streamable-http
mcp_servers:
ux-xd-llms-txt:
url: "https://llmstxtmcp.dev/mcp" {
"McpServers": {
"ux-xd-llms-txt": {
"Transport": "http",
"Url": "https://llmstxtmcp.dev/mcp"
}
}
} assistant mcp add ux-xd-llms-txt -t streamable-http -u 'https://llmstxtmcp.dev/mcp'
{
"mcpServers": {
"ux-xd-llms-txt": {
"type": "http",
"url": "https://llmstxtmcp.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 24 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 24 Sept 2026 · Probed https://llmstxtmcp.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of llmstxtmcp.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| llmstxtmcp.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://llmstxtmcp.dev/mcp | Unreachable | ||
| http (plaintext) | http://llmstxtmcp.dev/mcp | HTTPS enforced |
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 →
llms_index ~191
Find and parse the llms.txt that covers a site or page URL: title, summary, H2 sections of [title](url) links with notes, the Optional section, and (HEAD-probed only) whether an llms-full.txt exists. Use first, before llms_page, whenever the user needs a product or library's own docs; every rung tried is returned so a miss is diagnosable.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | Bypass the 24 h cache and fetch again. |
| site | string | yes | Site or page URL, e.g. "docs.stripe.com" or "https://hono.dev/docs/". The most specific covering llms.txt wins. |
| task_context | string | yes | One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need. |
No output schema declared.
No examples provided.
llms_page ~167
Return one docs page as markdown, paginated: tries Accept: text/markdown negotiation, the page's rel="alternate" markdown mirror, the .md / .html.md / index.md conventions, then a bounded HTML-to-markdown conversion. Use on the URLs llms_index returns, or on any docs URL you already hold.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | Characters of markdown to return in this call. |
| offset | integer | – | Character offset to continue from (use next_offset from a truncated result). |
| task_context | string | yes | One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need. |
| url | string | yes | Page URL (http/https). |
No output schema declared.
No examples provided.
llms_search ~180
Search the llms.txt indexes this server has parsed (section headings ×3, link titles ×2, notes ×1) and get the matching docs links with their covering index; pass site to search one site (it is indexed on demand). Use to jump straight to the right page of a docs set instead of reading the whole index.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| max_bytes | integer | – | Byte cap on the results array. |
| query | string | yes | Words to match against section headings, link titles and notes. |
| site | string | – | Restrict to one site (indexed via llms_index if not yet cached). |
| task_context | string | yes | One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need. |
No output schema declared.
No examples provided.
What is the llms.txt for agents MCP server?
llms.txt for agents is an MCP server listed in the public MCP registry as io.github.ux-xd/llms-txt. Any site's llms.txt: find the covering index, read its linked docs as markdown, search sections. This page covers its hosted endpoint (https://llmstxtmcp.dev/mcp).
Is the llms.txt for agents MCP server safe to use?
llms.txt for agents scores 0 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 for agents MCP server expose?
llms.txt for agents exposes 3 tools: llms_index, llms_page, llms_search. Their descriptions and schemas cost roughly 538 tokens of context every time the server is loaded.
Does the llms.txt for agents MCP server require authentication?
Its publisher declares no required credentials for llms.txt for agents. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the llms.txt for agents MCP server still maintained?
llms.txt for agents has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 16 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.