# Markdown Lane Check - llms.txt, .md twins, Accept: text/markdown (remote · www.pathwren.workers.dev)

Six checks: llms.txt, llms-full.txt, .md twins, Accept: text/markdown, sitemap.md, alt link. Free.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `www.pathwren.workers.dev`: 81/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-pathwren-www-markdown-lane-check/c-mcp-registry-official-mcp-markdown.md), [page](https://verifymcp.io/servers/dev-workers-pathwren-www-markdown-lane-check/c-mcp-registry-official-mcp-markdown)

## Channel facts

- Endpoint: `https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown`
- 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-09-21.

- **Endpoint Security**: 80/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 check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2870 tokens (~318/item across 9 items; 5 tools + 4 resources), over budget; trim descriptions and params.
  - Tools include usage examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 (60% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Markdown Lane Check - llms.txt, .md twins, Accept… MCP server?

Markdown Lane Check - llms.txt, .md twins, Accept… is a hosted endpoint at https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown, 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 dev-workers-pathwren-www-markdown-lane-check 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-pathwren-www-markdown-lane-check": {
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-pathwren-www-markdown-lane-check": {
      "type": "http",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-pathwren-www-markdown-lane-check]
url = "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-pathwren-www-markdown-lane-check": {
      "type": "remote",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-pathwren-www-markdown-lane-check --url 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-pathwren-www-markdown-lane-check:
    url: "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-pathwren-www-markdown-lane-check": {
      "Transport": "http",
      "Url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-pathwren-www-markdown-lane-check -t streamable-http -u 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-pathwren-www-markdown-lane-check": {
      "type": "http",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown"
    }
  }
}
```

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-20 (score 81, +1)

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

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

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

### 2026-09-16 (score 79, +1)

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

### 2026-09-14 (score 78, +1)

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

### 2026-09-11 (score 77, +1)

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

### 2026-09-09 (score 76, +1)

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

### 2026-09-08 (score 75, +7)

- [security improvement] Judged manipulation: unverified → pass
- [functional improvement] Schema quality: unverified → good

### 2026-09-07 (score 68, −6)

- [security regression] Judged manipulation: pass → unverified
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_markdown_lane” rewrote its description, which is the text the model reads
- [security] Tool “explain_llms_txt” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: good → unverified
- [functional improvement] Stability: unverified → 0.03

## MCP tools (5)

### `markdown_lane_self_report` (~487 tokens)

Have you taken the markdown lane here? (no arguments)

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"markdown_lane_self_report","arguments":{}}} — POST that exact body to https://www.pathwren.workers.dev/mcp/markdown and the answer is which markdown addresses YOUR client has fetched on this host and which pages it took as HTML instead — each one beside the .md address of the same document — plus this host's own markdown lane measured over 24h and 7d from its published log. THIS IS THE CALL TO MAKE FIRST on this server: it is the only one whose subject is the request you just sent, so there is nothing to look up and no argument to invent. No key, no account, no OAuth, no session to open first, read-only, and nothing for you to invent. Every fact is computed from your own headers and from files this host already publishes; nothing is fetched to build it, and no URL of yours is touched. Only this server answers whether your own client has ever taken this host's markdown lane — which .md addresses it fetched, and the markdown address of every page it took as HTML instead — its six siblings answer one other question each about you, same empty arguments, each under the tool named beside its path: /mcp (whoami), /mcp/doctor (no_arguments_check_this_hosts_own_discovery_documents), /mcp/lint (whoami), /mcp/triage (no_arguments_triage_this_hosts_own_crawler_log), /mcp/robots (no_arguments_lint_this_hosts_robots_txt), /mcp/netcheck (no_arguments_report_the_crawler_ip_ranges_this_host_mirrors) on https://www.pathwren.workers.dev; whoami is answered by all seven and is never an error, so one identical body still walks the whole family if you prefer that. Example: the complete call, exactly as written, nothing to fill in — {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"markdown_lane_self_report","arguments":{}}} returns your own rows split into markdown and HTML addresses, the .md twin of each page you took as HTML, and how many distinct external clients used this host's markdown lane in the last 2…

Output parameters:

- `answered_by` (object): Which server answered, at which endpoint, with which tool.
- `caveats` (array)
- `independent` (boolean)
- `license` (string)
- `this_call_touched` (object): Exactly which files were read. No third party is contacted.
- `we_book_you_as` (object): The class this host's own instrument records for that user-agent.
- `you` (object): The user-agent you sent and the address you came from.

### `whoami` (~277 tokens)

Who is calling? (no arguments)

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — POST that exact body to https://www.pathwren.workers.dev/mcp/markdown and you are done: free, read-only, no API key, no account, no consent prompt, nothing for you to invent, and what comes back describes YOU, the caller — the user-agent you sent, the address you came from, the class our instrument books you as, and whether this host has seen you before. Takes no arguments. Safe to call. Deterministic. Touches no third party. Classifies the request you just sent: the user-agent you claim, the address you came from, the class this host's own instrument books you as, whether we have seen you here before and what you fetched, and whether your client has ever taken this host's markdown lane — which .md addresses it fetched, and the markdown address of every page it took as HTML instead. Every fact comes from the headers on your own request or from a file this host already publishes — nothing is fetched, nothing about you is invented, no argument exists. Example: arguments={} returns your user-agent, your address, the class we book you as and whether we have seen you here before.

Output parameters:

- `answered_by` (object): Which server answered, at which endpoint.
- `caveats` (array): What this answer does NOT establish — a user-agent is a claim.
- `independent` (boolean): This host is independent and unaffiliated.
- `license` (string)
- `this_call_touched` (object): Exactly which files were read to answer. No third party is contacted.
- `we_book_you_as` (object): The class this host's own instrument records for that user-agent.
- `we_have_seen_you` (object): Whether this user-agent appears in the published observation window.
- `you` (object): The user-agent you sent and the address you came from.

### `example` (~303 tokens)

Run this server's worked example (no arguments)

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"example","arguments":{}}} — POST that exact body to https://www.pathwren.workers.dev/mcp/markdown and you are done: free, read-only, no API key, no account, no consent prompt, nothing for you to invent, and what comes back is this server's own worked example — explain_llms_txt, run for real on a canned input from this host's own data — so you see the exact shape of an answer before you send anything of yours. Takes no arguments. Safe to call. Deterministic. Touches no third party. Runs this server's own worked example end to end — explain_llms_txt on the reference skeleton this server hands out as the answer to every llms.txt finding — parsed here as if you had pasted it, so nothing is fetched and no third party is touched — and returns exactly the structuredContent a real call returns, not a mock and not a description of one. Use it to see the shape of an answer before you decide what to send. The input is canned from this host's own data; no URL of yours is fetched and no third party is touched. Example: arguments={} runs explain_llms_txt with {"text":"# Your project\n\n> One paragraph: what this is, who it is for, and what it is no and returns its real answer.

Output parameters:

- `answer` (object): The real structuredContent of that call, not a mock.
- `answered_by` (object)
- `input_came_from` (string): Where the canned input came from — always this host's own data.
- `license` (string)
- `ran` (object): The tool name and the exact arguments that were run.
- `reproduce` (string): A command that reproduces this answer.
- `this_is_not_a_mock` (string)
- `what_it_shows` (string)

### `check_markdown_lane` (~296 tokens)

Can an agent read this site as markdown?

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"markdown_lane_self_report","arguments":{}}} — Reads the markdown lane of a URL you name and returns six verdicts with the exact fix for each: /llms.txt, /llms-full.txt, the .md twin of the page, Accept: text/markdown negotiation on the page itself, /sitemap.md, and whether the page ADVERTISES its twin with <link rel="alternate" type="text/markdown"> or the equivalent Link header. Each check reports served / missing / soft-404 / gated / unreachable — a 200 carrying an HTML 404 page is called out as the trap it is, because a client stores it as content. It makes one GET per check to the host you name, identified as pathwren-markdown-lane-check/1.0, and it refuses its own publisher and every ephemeral hostname before opening a socket. Example: arguments={"url":"https://example.com/"} returns the six verdicts for that origin.

Input parameters:

- `url` (string, required): The page to check, e.g. https://example.com/docs/getting-started. The origin is used for /llms.txt and /sitemap.md; the exact path is used for the .md twin, the Accept negotiation and the alternate-l…

### `explain_llms_txt` (~275 tokens)

Parse and critique an llms.txt

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"markdown_lane_self_report","arguments":{}}} — Parses an llms.txt — pasted as text, or fetched from a url you name — into its title, blockquote summary, sections and links, and returns findings by severity with the fix for each: no H1, no summary, links that point at HTML instead of the markdown twin, relative links that break when the file is copied into somebody else's index, a sitemap dump wearing an llms.txt name, HTML tags in the body, duplicate targets, and a missing `## Optional` section on a long list. Returns a ready-to-edit skeleton with every answer. Pasted text is parsed in the request and discarded; nothing is stored. Example: arguments={"url":"https://example.com"} fetches https://example.com/llms.txt and critiques it.

Input parameters:

- `text` (string): The contents of an llms.txt. When present nothing is fetched at all.
- `url` (string): Where to read it from. A bare origin means <origin>/llms.txt; a full path to llms.txt or llms-full.txt is taken as given. Ignored when `text` is present.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-pathwren-www-markdown-lane-check/c-mcp-registry-official-mcp-markdown#diagnostics

## Score history

- 2026-09-21: 81
- 2026-09-20: 81
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 78
- 2026-09-14: 78
- 2026-09-13: 77
- 2026-09-12: 77
- 2026-09-11: 77
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 75
- 2026-09-07: 68
- 2026-09-06: 74

## Common questions

### What is the Markdown Lane Check - llms.txt, .md twins, Accept… MCP server?

Markdown Lane Check - llms.txt, .md twins, Accept… is an MCP server listed in the public MCP registry as dev.workers.pathwren.www/markdown-lane-check. Six checks: llms.txt, llms-full.txt, .md twins, Accept: text/markdown, sitemap.md, alt link. Free. This page covers its hosted endpoint (https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown).

### Is the Markdown Lane Check - llms.txt, .md twins, Accept… MCP server safe to use?

Markdown Lane Check - llms.txt, .md twins, Accept… scores 81 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 Markdown Lane Check - llms.txt, .md twins, Accept… MCP server expose?

Markdown Lane Check - llms.txt, .md twins, Accept… exposes 5 tools: markdown_lane_self_report, whoami, example, check_markdown_lane, explain_llms_txt. Their descriptions and schemas cost roughly 1,638 tokens of context every time the server is loaded.

### Does the Markdown Lane Check - llms.txt, .md twins, Accept… MCP server require authentication?

No. We connected to Markdown Lane Check - llms.txt, .md twins, Accept… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Markdown Lane Check - llms.txt, .md twins, Accept… MCP server still maintained?

Markdown Lane Check - llms.txt, .md twins, Accept… is still listed as active in the MCP registry. We last reached this channel on 21 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://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown
- Website: https://www.pathwren.workers.dev/c/mcp-registry-official/mcp-markdown.html
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-pathwren-www-markdown-lane-check/c-mcp-registry-official-mcp-markdown.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-pathwren-www-markdown-lane-check/c-mcp-registry-official-mcp-markdown.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-pathwren-www-markdown-lane-check/c-mcp-registry-official-mcp-markdown