# Agent Discovery Doctor - llms.txt, agent card, mcp.json (remote · www.pathwren.workers.dev)

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

- Trust score: 84/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`: 84/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-pathwren-www-agent-discovery-doctor/c-mcp-registry-official-mcp-doctor.md), [page](https://verifymcp.io/servers/dev-workers-pathwren-www-agent-discovery-doctor/c-mcp-registry-official-mcp-doctor)

## Channel facts

- Endpoint: `https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.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**: 82/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 3477 tokens (~289/item across 12 items; 8 tools + 4 resources), over budget; trim descriptions and params.
  - Tools include usage examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 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 (38% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 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.

### Claude

```bash
claude mcp add --transport http dev-workers-pathwren-www-agent-discovery-doctor 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-pathwren-www-agent-discovery-doctor": {
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-pathwren-www-agent-discovery-doctor": {
      "type": "http",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
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

```yaml
mcp_servers:
  dev-workers-pathwren-www-agent-discovery-doctor:
    url: "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-pathwren-www-agent-discovery-doctor": {
      "Transport": "http",
      "Url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor"
    }
  }
}
```

### Vellum

```bash
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'
```

### Other

```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 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 84, +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.

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

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

### 2026-09-14 (score 81, +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-12 (score 80, +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.

### 2026-09-09 (score 79, +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-07 (score 78, 0)

- [security] 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
- [functional regression] Schema quality: 224 → 289
- [functional improvement] Tool coverage: 29% → 38%
- [functional] New tool “no_arguments_check_this_hosts_own_discovery_documents”

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

- [security] 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

## MCP tools (8)

### `no_arguments_check_this_hosts_own_discovery_documents` (~460 tokens)

No arguments: the discovery check this server runs on a host you name, run on this host

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.

Output parameters:

- `answered_by` (object)
- `caveats` (array)
- `independent` (boolean)
- `license` (string)
- `no_request_was_made` (string)
- `reproduce` (string)
- `takes_no_arguments` (boolean)
- `this_call_touched` (object)
- `this_hosts_discovery_documents` (object): Per-document verdicts, the group rollup and the score.
- `to_do_this_for_your_own_host` (string)
- `what_is_missing_here` (array)
- `what_this_is` (string)
- `who_has_been_observed_asking_for_these` (object)

### `whoami` (~366 tokens)

Who is calling? — the one call that needs nothing from you

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

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` (~320 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/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.

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_discovery_documents` (~201 tokens)

Which discovery documents does this host serve?

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

Input parameters:

- `groups` (string): Subset: agent, mcp, api, web, or all (default).
- `host` (string, required): Hostname to check. https is assumed.
- `mcp_path` (string): MCP endpoint path, e.g. /mcp: also checks documents relative to it.

### `explain_document` (~137 tokens)

What is this document, and who reads it?

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.

Input parameters:

- `name` (string): Document name or path, e.g. owners.json. Omit for the catalogue.

### `validate_llms_txt` (~138 tokens)

Check a pasted llms.txt

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.

Input parameters:

- `text` (string, required): The llms.txt content itself, not a URL.

### `llms_txt_from_sitemap` (~190 tokens)

Draft an llms.txt from a sitemap

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

Input parameters:

- `max_per_section` (integer): Links per section, default 40.
- `summary` (string): The blockquote line.
- `title` (string): H1 to use; default from the hostname.
- `xml` (string, required): The sitemap XML, or a plain list of URLs.

### `validate_agent_card` (~130 tokens)

Check a pasted A2A agent card

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.

Input parameters:

- `json` (string, required): The agent card JSON itself, not a URL.

## Diagnostics

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

## Score history

- 2026-09-21: 84
- 2026-09-20: 84
- 2026-09-19: 83
- 2026-09-18: 83
- 2026-09-17: 82
- 2026-09-16: 82
- 2026-09-15: 81
- 2026-09-14: 81
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 79
- 2026-09-08: 78
- 2026-09-07: 78
- 2026-09-06: 78
- 2026-09-05: 77
- 2026-09-04: 77
- 2026-09-03: 76
- 2026-09-02: 76
- 2026-09-01: 77

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

## Links

- Remote endpoint: https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor
- Website: https://www.pathwren.workers.dev/c/mcp-registry-official/mcp-doctor.html
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-pathwren-www-agent-discovery-doctor/c-mcp-registry-official-mcp-doctor.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-pathwren-www-agent-discovery-doctor/c-mcp-registry-official-mcp-doctor.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-pathwren-www-agent-discovery-doctor/c-mcp-registry-official-mcp-doctor