Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Markdown Lane Check - llms.txt, .md twins, Accept: text/markdown

REMOTE · WWW.PATHWREN.WORKERS.DEV · SCANNED SEP 21

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

+3 this week 81 Trust /100
Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Tools include usage examples.Pass
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 (60% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
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.

remote · www.pathwren.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-pathwren-www-markdown-lane-check 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-workers-pathwren-www-markdown-lane-check": {
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-workers-pathwren-www-markdown-lane-check": {
      "type": "http",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
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/config.yaml
mcp_servers:
  dev-workers-pathwren-www-markdown-lane-check:
    url: "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-workers-pathwren-www-markdown-lane-check": {
      "Transport": "http",
      "Url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown"
    }
  }
}
# add to Vellum
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'
// mcp.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 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.

  • 20 Sept 26 +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.

  • 18 Sept 26 +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.

  • 16 Sept 26 +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.

  • 14 Sept 26 +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.

  • 11 Sept 26 +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.

  • 9 Sept 26 +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.

  • 8 Sept 26 +7
    • Judged manipulation: unverified → pass security
    • Schema quality: unverified → good functional
  • 7 Sept 26 −6
    • 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 security
    • Schema quality: good → unverified functional
    • Stability: unverified → 0.03 functional
Diagnostics

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 21 Sept 2026 · Probed https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pathwren.workers.dev CN=WE1,O=Google Trust Services,C=US 31 Aug 2026 29 Nov 2026 ECDSA 256 ECDSA-SHA256 7beee86e7f102c1e0e48318ca5b2eaa1
SANs: pathwren.workers.dev, *.pathwren.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.pathwren.workers.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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=31536000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown Verified 200
http (plaintext) http://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown HTTPS enforced 301 https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/markdown
MCP tools · 5 exposed · ~1,638 tokens

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 →

Tool Tokens
check_markdown_lane ~296

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.

NameTypeReqDescription
urlstringyesThe 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…

No output schema declared.

{"url":"https://example.com/"}
example ~303

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
answerobjectyesThe real structuredContent of that call, not a mock.
answered_byobjectyes
input_came_fromstringyesWhere the canned input came from — always this host's own data.
licensestringyes
ranobjectyesThe tool name and the exact arguments that were run.
reproducestringyesA command that reproduces this answer.
this_is_not_a_mockstringyes
what_it_showsstringyes
{}
explain_llms_txt ~275

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.

NameTypeReqDescription
textstringThe contents of an llms.txt. When present nothing is fetched at all.
urlstringWhere 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.

No output schema declared.

{"url":"https://example.com"}
markdown_lane_self_report ~487

{"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…

Input schema present but exposes no named parameters.

NameTypeReqDescription
answered_byobjectyesWhich server answered, at which endpoint, with which tool.
caveatsarrayyes
independentbooleanyes
licensestringyes
this_call_touchedobjectyesExactly which files were read. No third party is contacted.
we_book_you_asobjectyesThe class this host's own instrument records for that user-agent.
youobjectyesThe user-agent you sent and the address you came from.
{}
whoami ~277

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
answered_byobjectyesWhich server answered, at which endpoint.
caveatsarrayyesWhat this answer does NOT establish — a user-agent is a claim.
independentbooleanyesThis host is independent and unaffiliated.
licensestringyes
this_call_touchedobjectyesExactly which files were read to answer. No third party is contacted.
we_book_you_asobjectyesThe class this host's own instrument records for that user-agent.
we_have_seen_youobjectyesWhether this user-agent appears in the published observation window.
youobjectyesThe user-agent you sent and the address you came from.
{}
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.