Dev tools · Official remote MCP server

The Robots.txt Policy Lint MCP server,
connected in one click.

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

Connect Robots.txt Policy Lint free How it works

Free to start · No credit card · No hosting needed

Use this server

Add Robots.txt Policy Lint 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 robots-txt-policy-lint https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/robots

Run in your terminal, then restart Claude Code.

Robots.txt Policy Lint · https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/robots

What you can do

What your AI can do with Robots.txt Policy Lint

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

“Use “lint_robots_txt”: FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Parse a robots.txt you paste and report every fault that makes it do something.”

“Use “check_path_allowed”: FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Evaluate a pasted robots.txt for one crawler and one or more paths under RFC 9.”

“Use “audit_ai_access”: FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Evaluate a pasted robots.txt against every AI crawler in this index and return.”

“Use “diff_robots_txt”: FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Compare two versions of a robots.txt and report only the crawlers whose verdic.”

Security check

How secure is the Robots.txt Policy Lint MCP server?

Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Robots.txt Policy Lint holds up.

✓ Verified directory serverRobots.txt Policy Lint · workers.dev

Official endpoint

Operated by Robots.txt Policy Lint (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 Robots.txt Policy Lint adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.

Run the free scanner on Robots.txt Policy Lint'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 Robots.txt Policy Lint

Choose Robots.txt Policy Lint in the gate directory. No sign-in needed.

Use it anywhere

Robots.txt Policy Lint's tools are live in every AI client you've connected — with rules and logging built in.

Connect Robots.txt Policy Lint free

Free to start · No credit card · No hosting needed

Straight from the server

The actual tools Robots.txt Policy Lint exposes

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

lint_robots_txt — FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Parse a robots.txt you paste and report every fault that makes it do something

check_path_allowed — FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Evaluate a pasted robots.txt for one crawler and one or more paths under RFC 9

audit_ai_access — FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Evaluate a pasted robots.txt against every AI crawler in this index and return

diff_robots_txt — FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Compare two versions of a robots.txt and report only the crawlers whose verdic

merge_policy — FIRST CALL, needs nothing: {"name":"whoami","arguments":{}} — Merge one of eight maintained robots.txt stances (block-ai-training, allow-ai-

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 Robots.txt Policy Lint MCP server?

workers.dev

Homepage More servers from workers.dev →

Own this server? Claim the listing →

Server facts

The Robots.txt Policy Lint MCP server at a glance

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

Operated byRobots.txt Policy Lint (workers.dev)

CategoryDev tools

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 Robots.txt Policy Lint MCP server?

Yes — Robots.txt Policy Lint 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 Robots.txt Policy Lint to Claude or ChatGPT?

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

Do I need to host anything?

No. Robots.txt Policy Lint runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.

Is the Robots.txt Policy Lint 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.