# Crawler Log Triage (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-crawler-log-triage/c-mcp-registry-official-mcp-triage.md), [page](https://verifymcp.io/servers/dev-workers-pathwren-www-crawler-log-triage/c-mcp-registry-official-mcp-triage)

## Channel facts

- Endpoint: `https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.7.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 4081 tokens (~313/item across 13 items; 9 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 (44% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 Crawler Log Triage MCP server?

Crawler Log Triage is a hosted endpoint at https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage, 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-crawler-log-triage 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-pathwren-www-crawler-log-triage": {
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-pathwren-www-crawler-log-triage": {
      "type": "http",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-pathwren-www-crawler-log-triage]
url = "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-workers-pathwren-www-crawler-log-triage --url 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-pathwren-www-crawler-log-triage:
    url: "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-pathwren-www-crawler-log-triage": {
      "Transport": "http",
      "Url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-pathwren-www-crawler-log-triage -t streamable-http -u 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-pathwren-www-crawler-log-triage": {
      "type": "http",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage"
    }
  }
}
```

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-13 (score 80, 0)

- [security] Tool “find_impersonators” rewrote its description, which is the text the model reads

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

- [security] Tool “find_impersonators” rewrote its description, which is the text the model reads

### 2026-09-10 (score 79, 0)

- [security] Tool “find_impersonators” rewrote its description, which is the text the model reads

### 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. Other categories moved too: Schema Quality & AI Usability rose 1.

## MCP tools (9)

### `no_arguments_triage_this_hosts_own_crawler_log` (~538 tokens)

No arguments: triage this host's own published crawler log

TAKES NO ARGUMENTS. POST {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_triage_this_hosts_own_crawler_log","arguments":{}}} to https://www.pathwren.workers.dev/mcp/triage — the answer is the triage of THIS host's own published request log — every operator in it run through the same parser, the same crawler index and the same operator-prefix verification that triage_log applies to a file you paste, rolled up by operator, by category and by crawler, with the share no index entry matches at all and the browser-shaped strings named separately. 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. The other zero-argument call on this server is triage_my_request, same empty arguments, which answers your own request triaged as one line of an access log — the crawler this host's index identifies from your user-agent, its operator and category, and whether the address you came from verifies against that operator's published prefixes. 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/doctor (no_arguments_check_this_hosts_own_discovery_documents), /mcp/lint (whoami), /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_triage_this_hosts_own_crawler_log","argume…

Output parameters:

- `answered_by` (object)
- `caveats` (array)
- `independent` (boolean)
- `license` (string)
- `no_address_was_triaged` (string)
- `reproduce` (string)
- `rollup` (object): Requests by operator, by category and by crawler, with the identified share.
- `takes_no_arguments` (boolean)
- `the_log_triaged` (object): Where the log came from, how it was parsed, and what it covers.
- `this_call_touched` (object)
- `to_do_this_for_your_own_file` (string)
- `what_no_index_entry_matched` (object)
- `what_this_is` (string)

### `triage_my_request` (~460 tokens)

Triage my own request (no arguments)

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"triage_my_request","arguments":{}}} — POST that exact body to https://www.pathwren.workers.dev/mcp/triage and the answer is your own request triaged as one line of an access log — the crawler this host's index identifies from your user-agent, its operator and category, and whether the address you came from verifies against that operator's published prefixes. 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 your own request triaged as one line of an access log, by the same parser and the same index that read a whole file — 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/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; 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":"triage_my_request","arguments":{}}} returns the single log line built from your address and your user-agent, the triage row for it, and the same rollup triage_log returns for a whole file.

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` (~356 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/triage 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: the request you just made, run through triage_log as a single log line, naming the crawler it identifies, its operator and category, and whether your address verifies against that operator's published prefixes. 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/doctor (no_arguments_check_this_hosts_own_discovery_documents), /mcp/lint (whoami), /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 your own request triaged as one line of an access log, by the same parser and the same index that read a whole file.

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` (~336 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/triage 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 — triage_log, 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 — triage_log on three lines in three of the five formats this parser accepts: an address Google publishes, an address in no published range claiming to be the same crawler, and a `uniq -c` count — all of it constants in this file, checked against our own mirror, with nothing fetched 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 triage_log with {"log":"66.249.66.1 Googlebot/2.1\n203.0.113.9 Googlebot/2.1\n412 GPTBot/1.2"} 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)

### `triage_log` (~199 tokens)

Triage a paste of log lines

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_triage_this_hosts_own_crawler_log","arguments":{}}} — Paste log lines — combined, JSON, `uniq -c`, `<ip> <ua>` or bare user-agents, auto-detected — for per-line crawler, operator, purpose and cost of blocking, a rollup by operator and category, and every line whose address contradicts its claim. Log text, never a URL. Example: log='66.249.66.1 Googlebot/2.1' returns Googlebot, Google, search, verified.

Input parameters:

- `detail` (string): Per-line table, or aggregates only.
- `limit` (integer): Max rows, default 200.
- `log` (string, required): The log text, up to 5000 lines. Mixed formats are fine.

### `find_impersonators` (~154 tokens)

Find the lines that are lying

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_triage_this_hosts_own_crawler_log","arguments":{}}} — Only the lines claiming a crawler whose operator publishes address ranges, from an address in none of them — 1997 IPv4 and 1062 IPv6 prefixes, 15 sources. Reverse-DNS operators come back with the command to run: this server makes no outbound request. Example: log='203.0.113.9 Googlebot/2.1' returns one impersonation.

Input parameters:

- `log` (string, required): The log text. Lines need an address to be checkable.

### `summarize_by_operator` (~141 tokens)

Roll a log up by operator and category

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_triage_this_hosts_own_crawler_log","arguments":{}}} — Aggregate only: who crawled you, how many requests each, what share, which category, and what blocking each would cost. Eats a `uniq -c` table straight from a shell pipeline. Example: log='412 GPTBot/1.2' returns OpenAI, 412 requests, 100%, ai-training.

Input parameters:

- `log` (string, required): Log text, or a `uniq -c` user-agent table.

### `robots_from_log` (~144 tokens)

robots.txt from a log

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_triage_this_hosts_own_crawler_log","arguments":{}}} — A robots.txt naming only the crawlers in your log, each with its request count and cost of blocking, plus a warning for any that do not documentably obey it — there the file is a request, not enforcement. Example: log='412 GPTBot/1.2', stance='block-ai-training' blocks GPTBot only.

Input parameters:

- `log` (string, required): The log text.
- `stance` (string): Default block-ai-training.

### `waf_ruleset_from_log` (~186 tokens)

WAF ruleset from a log

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_triage_this_hosts_own_crawler_log","arguments":{}}} — nginx, Caddy, Cloudflare, HAProxy or Apache rules for only the crawlers in your log. The reply warns that a UA rule stops only an honest client, and that impersonation is an address problem needing the published prefixes as an allowlist. Example: log='412 GPTBot/1.2', target='nginx', scope='ai-training'.

Input parameters:

- `action` (string): Default block.
- `log` (string, required): The log text.
- `scope` (string): A category (default ai-training), 'all-seen', 'impersonators', or a stance.
- `target` (string): Default nginx.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-pathwren-www-crawler-log-triage/c-mcp-registry-official-mcp-triage#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: 77
- 2026-09-06: 77
- 2026-09-05: 77
- 2026-09-04: 76
- 2026-09-03: 76
- 2026-09-02: 76
- 2026-09-01: 76

## Common questions

### What is the Crawler Log Triage MCP server?

Crawler Log Triage is an MCP server listed in the public MCP registry as dev.workers.pathwren.www/crawler-log-triage. {"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/triage).

### Is the Crawler Log Triage MCP server safe to use?

Crawler Log Triage 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 Crawler Log Triage MCP server expose?

Crawler Log Triage exposes 9 tools: no_arguments_triage_this_hosts_own_crawler_log, triage_my_request, whoami, example, triage_log, and 4 more. Their descriptions and schemas cost roughly 2,514 tokens of context every time the server is loaded.

### Does the Crawler Log Triage MCP server require authentication?

No. We connected to Crawler Log Triage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Crawler Log Triage MCP server still maintained?

Crawler Log Triage 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/triage
- Website: https://www.pathwren.workers.dev/c/mcp-registry-official/mcp-triage.html
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-pathwren-www-crawler-log-triage/c-mcp-registry-official-mcp-triage.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-pathwren-www-crawler-log-triage/c-mcp-registry-official-mcp-triage.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-pathwren-www-crawler-log-triage/c-mcp-registry-official-mcp-triage