# llms.txt for agents (remote · llmstxtmcp.dev)

Any site's llms.txt: find the covering index, read its linked docs as markdown, search sections.

- Trust score: 0/100 (low)
- Change this week: −76
- Registry status: active
- Liveness: dead
- Owner verified: no
- Last scored: 2026-09-24

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

## Components

- remote · `llmstxtmcp.dev`: 0/100 (this document), [markdown](https://verifymcp.io/servers/ux-xd-llms-txt/llmstxtmcp.md), [page](https://verifymcp.io/servers/ux-xd-llms-txt/llmstxtmcp)

## Channel facts

- Endpoint: `https://llmstxtmcp.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

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

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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

## Install

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

### Claude

```bash
claude mcp add --transport http ux-xd-llms-txt 'https://llmstxtmcp.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ux-xd-llms-txt": {
      "url": "https://llmstxtmcp.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ux-xd-llms-txt": {
      "type": "http",
      "url": "https://llmstxtmcp.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ux-xd-llms-txt]
url = "https://llmstxtmcp.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ux-xd-llms-txt": {
      "type": "remote",
      "url": "https://llmstxtmcp.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ux-xd-llms-txt --url 'https://llmstxtmcp.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ux-xd-llms-txt:
    url: "https://llmstxtmcp.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ux-xd-llms-txt": {
      "Transport": "http",
      "Url": "https://llmstxtmcp.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ux-xd-llms-txt -t streamable-http -u 'https://llmstxtmcp.dev/mcp'
```

### Other

```json
{
  "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.

## 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-09-24 (score 0, −15)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-23 (score 15, −15)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-22 (score 30, −16)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-20 (score 46, −15)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-19 (score 61, −15)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-17 (score 76, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.47 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-15 (score 76, +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.

### 2026-09-13 (score 75, +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.

## MCP tools (3)

### `llms_index` (~191 tokens)

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.

Input parameters:

- `refresh` (boolean): Bypass the 24 h cache and fetch again.
- `site` (string, required): Site or page URL, e.g. "docs.stripe.com" or "https://hono.dev/docs/". The most specific covering llms.txt wins.
- `task_context` (string, required): 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.

### `llms_page` (~167 tokens)

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.

Input parameters:

- `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, required): 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, required): Page URL (http/https).

### `llms_search` (~180 tokens)

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.

Input parameters:

- `limit` (integer)
- `max_bytes` (integer): Byte cap on the results array.
- `query` (string, required): 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, required): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ux-xd-llms-txt/llmstxtmcp#diagnostics

## Score history

- 2026-09-24: 0
- 2026-09-23: 15
- 2026-09-22: 30
- 2026-09-21: 46
- 2026-09-20: 46
- 2026-09-19: 61
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 76
- 2026-09-15: 76
- 2026-09-14: 75
- 2026-09-13: 75
- 2026-09-12: 74
- 2026-09-11: 74
- 2026-09-10: 73
- 2026-09-09: 73
- 2026-09-08: 72
- 2026-09-07: 72
- 2026-09-06: 71
- 2026-09-05: 71
- 2026-09-04: 71
- 2026-09-03: 70
- 2026-09-02: 63

## Common questions

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

## Links

- Remote endpoint: https://llmstxtmcp.dev/mcp
- Repository: https://github.com/ux-xd/llms-txt-mcp
- Website: https://llmstxtmcp.dev/
- Changelog RSS feed: https://verifymcp.io/servers/ux-xd-llms-txt/llmstxtmcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ux-xd-llms-txt/llmstxtmcp.json
- HTML version of this page: https://verifymcp.io/servers/ux-xd-llms-txt/llmstxtmcp