Community · Official remote MCP server

The Crawler Log Triage MCP server,
connected in one click.

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key. Connect the official Crawler Log Triage MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.

Connect Crawler Log Triage free How it works

Free to start · No credit card · No hosting needed

Use this server

Add Crawler Log Triage to your AI in one minute

Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.

claude mcp add --transport http crawler-log-triage https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage

Run in your terminal, then restart Claude Code.

Crawler Log Triage · https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage

What you can do

What your AI can do with Crawler Log Triage

Real prompts you can type the moment it's connected — no setup, no docs to read.

“Use “triage_log”: FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Paste log lines — combined, JSON, `uniq -c`, `<ip> <ua>` or bare user-agents,.”

“Use “find_impersonators”: FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Only the lines claiming a crawler whose operator publishes address ranges, fro.”

“Use “summarize_by_operator”: FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Aggregate only: who crawled you, how many requests each, what share, which cat.”

“Use “robots_from_log”: FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — A robots.txt naming only the crawlers in your log, each with its request count.”

Security check

How secure is the Crawler Log Triage MCP server?

Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Crawler Log Triage holds up.

✓ Verified directory serverCrawler Log Triage · workers.dev

Official endpoint

Operated by Crawler Log Triage (workers.dev) at its documented MCP endpoint — not a third-party mirror or community re-host.

No sign-in needed

This server only exposes public data — no account and no credentials are involved when you connect.

Scanned before it goes live

gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.

Watched for drift

If Crawler Log Triage adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.

Run the free scanner on Crawler Log Triage's server →

How it works

Connected in three steps

Connect your gate

Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.

Pick Crawler Log Triage

Choose Crawler Log Triage in the gate directory. No sign-in needed.

Use it anywhere

Crawler Log Triage's tools are live in every AI client you've connected — with rules and logging built in.

Connect Crawler Log Triage free

Free to start · No credit card · No hosting needed

Straight from the server

The actual tools Crawler Log Triage exposes

Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.

triage_log — FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Paste log lines — combined, JSON, `uniq -c`, `<ip> <ua>` or bare user-agents,

find_impersonators — FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Only the lines claiming a crawler whose operator publishes address ranges, fro

summarize_by_operator — FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Aggregate only: who crawled you, how many requests each, what share, which cat

robots_from_log — FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — A robots.txt naming only the crawlers in your log, each with its request count

waf_ruleset_from_log — FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — nginx, Caddy, Cloudflare, HAProxy or Apache rules for only the crawlers in you

whoami — {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — POST that exact body to https://www.pathwren.work

example — {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"example","arguments":{}}} — POST that exact body to https://www.pathwren.wor

Author

Who runs the Crawler Log Triage MCP server?

workers.dev

Homepage More servers from workers.dev →

Own this server? Claim the listing →

Server facts

The Crawler Log Triage MCP server at a glance

Endpointhttps://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage

Operated byCrawler Log Triage (workers.dev)

CategoryCommunity

Sign-inNone — public data only

Available in gateYes — one-click connect

Works withClaude, ChatGPT, Cursor & any MCP client

FAQ

Questions, answered

Is there an official Crawler Log Triage MCP server?

Yes — Crawler Log Triage operates its own remote MCP server at www.pathwren.workers.dev. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.

How do I connect Crawler Log Triage to Claude or ChatGPT?

Add gate's gateway URL to your AI client once, then pick Crawler Log Triage in the directory. No account or sign-in is needed. From then on, Crawler Log Triage's tools are available in every client you've connected to gate.

Do I need to host anything?

No. Crawler Log Triage runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.

Is the Crawler Log Triage MCP server safe to connect?

It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.