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.

Agent Discovery Doctor - llms.txt, agent card, mcp.json

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

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key

+3 this week 84 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 Usability82
  • 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 3477 tokens (~289/item across 12 items; 8 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Tools include usage examples.Pass
Stability & Change Management67
  • Stability observed for 20 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 (38% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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 Agent Discovery Doctor - llms.txt, agent card, mcp.json server?

Agent Discovery Doctor - llms.txt, agent card, mcp.json is a hosted endpoint at https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor, 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-agent-discovery-doctor 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-workers-pathwren-www-agent-discovery-doctor": {
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-workers-pathwren-www-agent-discovery-doctor": {
      "type": "http",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-workers-pathwren-www-agent-discovery-doctor]
url = "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-pathwren-www-agent-discovery-doctor": {
      "type": "remote",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-workers-pathwren-www-agent-discovery-doctor --url 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-workers-pathwren-www-agent-discovery-doctor:
    url: "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-workers-pathwren-www-agent-discovery-doctor": {
      "Transport": "http",
      "Url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor"
    }
  }
}
# add to Vellum
assistant mcp add dev-workers-pathwren-www-agent-discovery-doctor -t streamable-http -u 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor'
// mcp.json
{
  "mcpServers": {
    "dev-workers-pathwren-www-agent-discovery-doctor": {
      "type": "http",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor"
    }
  }
}

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 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 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.

  • 12 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.

  • 9 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.

  • 7 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_discovery_documents” rewrote its description, which is the text the model reads security
    • Tool “explain_document” rewrote its description, which is the text the model reads security
    • Tool “llms_txt_from_sitemap” rewrote its description, which is the text the model reads security
    • Tool “validate_agent_card” rewrote its description, which is the text the model reads security
    • Tool “validate_llms_txt” rewrote its description, which is the text the model reads security
    • Tool “whoami” rewrote its description, which is the text the model reads security
    • Schema quality: 224 → 289 functional
    • Tool coverage: 29% → 38% functional
    • New tool “no_arguments_check_this_hosts_own_discovery_documents” functional
  • 6 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “whoami” rewrote its description, which is the text the model reads security
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/doctor

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/doctor Verified 200
http (plaintext) http://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor HTTPS enforced 301 https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor
MCP tools · 8 exposed · ~1,942 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_discovery_documents ~201

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_check_this_hosts_own_discovery_documents","arguments":{}}} — Probes 22 documents agents and trust indexes ask for — llms.txt, agent card, owners.json, oauth metadata, mcp.json, apis.json, openapi, robots, sitemap — as served, missing, gated or 200-with-HTML soft-404, and says who asks for each missing one. Refuses private, ephemeral and its own hosts. Example: host='example.com'.

NameTypeReqDescription
groupsstringSubset: agent, mcp, api, web, or all (default).
hoststringyesHostname to check. https is assumed.
mcp_pathstringMCP endpoint path, e.g. /mcp: also checks documents relative to it.

No output schema declared.

{"host":"example.com"}
example ~320

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"example","arguments":{}}} — POST that exact body to https://www.pathwren.workers.dev/mcp/doctor 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 — validate_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 — validate_llms_txt on a four-line llms.txt held as a constant in this file: it exercises the H1, the blockquote summary and an H2 link section, which is the whole format — and it fetches nothing, from us or from anyone — 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 validate_llms_txt with {"text":"# Site\n\n> One line.\n\n## Docs\n\n- [Guide](https://e.com/g): start here."} 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_document ~137

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_check_this_hosts_own_discovery_documents","arguments":{}}} — One catalogue entry: what the document is for, the named clients observed asking this host for it with dates and the status they took, what a 404 costs, and the spec URL. No argument lists all 22. Example: name='owners.json' names the bot that asks for it twice.

NameTypeReqDescription
namestringDocument name or path, e.g. owners.json. Omit for the catalogue.

No output schema declared.

{"name":"owners.json"}
llms_txt_from_sitemap ~190

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_check_this_hosts_own_discovery_documents","arguments":{}}} — Paste sitemap.xml, or one URL per line, and get a draft llms.txt: URLs grouped into H2 sections by path, titles from slugs, lastmod kept, and a TODO wherever only you can write the sentence. A sitemap index is reported as one. Example: xml='https://e.com/docs/a\nhttps://e.com/blog/b'.

NameTypeReqDescription
max_per_sectionintegerLinks per section, default 40.
summarystringThe blockquote line.
titlestringH1 to use; default from the hostname.
xmlstringyesThe sitemap XML, or a plain list of URLs.

No output schema declared.

{"xml":"https://e.com/docs/a\nhttps://e.com/blog/b"}
no_arguments_check_this_hosts_own_discovery_documents ~460

TAKES NO ARGUMENTS. POST {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_check_this_hosts_own_discovery_documents","arguments":{}}} to https://www.pathwren.workers.dev/mcp/doctor — the answer is the whole agent-discovery catalogue checked against THIS host — every document this server tracks, whether this host serves it, its size and content type, which ones are missing, and the part only this server can add: the named clients it has watched ask for each file, when, and the status that request took. There is nothing to fill in: the input schema is literally empty, `arguments: {}` and no `arguments` key at all both work, and the subject is a file this host already publishes, so the answer does not depend on you at all. No key, no account, no OAuth, no session to open first, read-only, and nothing for you to invent. Nothing is fetched to build it — no request leaves this edge, and none is made to you. whoami and example are here too and take nothing either. Every other tool on this server wants a file pasted in; this one wants nothing. The siblings answer one question each under the tool named beside them: /mcp (whoami), /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), /mcp/markdown (markdown_lane_self_report). Example: the complete call, exactly as written, nothing to fill in — {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_check_this_hosts_own_discovery_documents","arguments":{}}} returns a present/missing verdict per tracked document with its byte size, the group each belongs to, the score out of the catalogue, and the observed askers per document with the date and status each one got.

Input schema present but exposes no named parameters.

NameTypeReqDescription
answered_byobjectyes
caveatsarrayyes
independentbooleanyes
licensestringyes
no_request_was_madestringyes
reproducestringyes
takes_no_argumentsbooleanyes
this_call_touchedobjectyes
this_hosts_discovery_documentsobjectyesPer-document verdicts, the group rollup and the score.
to_do_this_for_your_own_hoststring
what_is_missing_herearrayyes
what_this_isstringyes
who_has_been_observed_asking_for_theseobjectyes
{}
validate_agent_card ~130

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_check_this_hosts_own_discovery_documents","arguments":{}}} — Validates a pasted /.well-known/agent-card.json against the nine fields A2A marks required and each skill's id/name/description/tags, and warns on capabilities declared true that a reader will then try. Example: json='{"name":"a"}' returns the eight missing fields.

NameTypeReqDescription
jsonstringyesThe agent card JSON itself, not a URL.

No output schema declared.

{"json":"{\"name\":\"My Agent\"}"}
validate_llms_txt ~138

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_check_this_hosts_own_discovery_documents","arguments":{}}} — Checks pasted llms.txt against the format: one H1, a blockquote summary, H2 sections of `- [name](url): notes`. Errors and warnings with line numbers and fixes, plus the parsed links. Text in, nothing fetched. Example: text='# Site' warns it has no summary and no sections.

NameTypeReqDescription
textstringyesThe llms.txt content itself, not a URL.

No output schema declared.

{"text":"# Site\n\n\u003e One line.\n\n## Docs\n\n- [Guide](https://e.com/g): start here."}
whoami ~366

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — POST that to https://www.pathwren.workers.dev/mcp/doctor and the answer is the user-agent you sent, the class this host's own instrument books it as, whether we have logged you here before — and the part only this server can answer: which of the discovery documents this catalogue tracks (llms.txt, the agent card, mcp.json, apis.json, oauth-protected-resource…) a client like yours has been observed asking THIS host for, when, and what status it took. Takes no arguments. Safe to call. Deterministic. Touches no third party. Nothing is fetched to build it: every fact comes from the headers on your own request or from a file this host already publishes. Only this server answers the last part — its five siblings answer one other question each about you, same empty arguments, each under the tool named beside its path: /mcp (whoami), /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), /mcp/markdown (markdown_lane_self_report) on https://www.pathwren.workers.dev. Example: arguments={} returns your user-agent, your address, the class we book you as, whether we have seen you here before, and which agent-discovery documents this host has watched a client like yours ask for — the dates, and the status each request took.

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 Agent Discovery Doctor - llms.txt, agent card, mcp.json server?

Agent Discovery Doctor - llms.txt, agent card, mcp.json is listed in the public MCP registry as dev.workers.pathwren.www/agent-discovery-doctor. {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key. This page covers its hosted endpoint (https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor).

Is the Agent Discovery Doctor - llms.txt, agent card, mcp.json server safe to use?

Agent Discovery Doctor - llms.txt, agent card, mcp.json scores 84 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 Agent Discovery Doctor - llms.txt, agent card, mcp.json server expose?

Agent Discovery Doctor - llms.txt, agent card, mcp.json exposes 8 tools: no_arguments_check_this_hosts_own_discovery_documents, whoami, example, check_discovery_documents, explain_document, and 3 more. Their descriptions and schemas cost roughly 1,942 tokens of context every time the server is loaded.

Does the Agent Discovery Doctor - llms.txt, agent card, mcp.json server require authentication?

No. We connected to Agent Discovery Doctor - llms.txt, agent card, mcp.json without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Agent Discovery Doctor - llms.txt, agent card, mcp.json server still maintained?

Agent Discovery Doctor - llms.txt, agent card, mcp.json 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.