mcpbeat Sign in

Doorman MCP Server

by clawhard Your server? Claim it
answering

Doorman is answering right now. Last checked 8 min ago. It exposes 3 tools.

Check which AI bots a site lets in, then write a fixed robots.txt.

Uptime history 5 hours of history
5 hours agonow
100.0%
Uptime 24h
17 of 17 checks
3
Tools
read from the server
84 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Doorman every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add doorman --transport http https://doorman.clawhard.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://doorman.clawhard.com/mcp
~/.codex/config.toml
[mcp_servers.doorman]
url = "https://doorman.clawhard.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "doorman": {
      "url": "https://doorman.clawhard.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "doorman": {
      "type": "http",
      "url": "https://doorman.clawhard.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

doorman
doorman_check_ai_bot_access
Use when the user asks whether their site (or any public site) blocks ChatGPT, Claude, Google AI, Perplexity or other AI crawlers, whether AI can read or train on their content, or why AI search does not mention their site. Fetches the live robots.txt and reports, for 22 named AI bots in four groups (AI training, AI search, assistants, search engines), which are let in, kept out or partly blocked, plus the site's content-signal preference and fixes. Example: {"url": "example.com"}. Read-only. To write a new robots.txt use doorman_write_robots_txt.
doorman_check_robots_txt
Use when the user pastes the text of a robots.txt (or you have drafted one) and asks which AI bots it lets in or blocks, or whether a change does what they want. Parses it the way crawlers do (groups, wildcards, longest-match) and reports each of 22 named AI bots as let in, kept out or partly blocked, with notes and a suggested choice. Pure parsing, no network. Example: {"robots_txt": "User-agent: GPTBot\nDisallow: /"}.
doorman_write_robots_txt
Use when the user wants to allow or block AI training, AI search or assistant bots on their site and needs the robots.txt lines. Takes an optional existing robots.txt plus a choice of "in" or "out" for each of three groups (training, ai_search, assistants) and returns a complete robots.txt that keeps existing rules, adds one clean group per choice and a shared content-signal line. Example: {"training": "out", "ai_search": "in", "assistants": "in"}. Returns text to paste at /robots.txt; it does not change any site.

Endpoints

URLTransportStateLatencyChecked
https://doorman.clawhard.com/mcp streamable-http answering 206 ms 8 min ago

Alternatives to Doorman

same job, measured the same way
Parallel World
by migurei-pw

Check which AI bots a site's robots.txt allows; read-only facts about Parallel World

3 tools answering
Agent Ready Website Check
by sadri-dridi

Check whether a website is readable by AI agents: robots, llms.txt, sitemap, HTML. Bounded.

31 tools answering
Website Tech Stack, SEO & llms.txt Check
by fairquery

Website tech stack, SEO issues, robots.txt AI-bot rules, sitemap and llms.txt in one call.

answering
Agent Access Door Check
by textforagents

Before your agent sets out, ask whether the site will let it in

5 tools answering
AI Site Scorer
by minglesai

Check website AI-readiness: Schema.org, llms.txt, E-E-A-T, robots.txt. Works in Cursor & Claude.

5 tools answering
A
Agent-readiness check
by wondaverse

Checks a website for AI agents: robots.txt, llms.txt, MCP, A2A. Ranked fixes, text to paste.

1 tools answering
Matchstick
by astralchemist

Checks a site build: sitemaps, structured data, robots.txt and what crawlers see.

651 installs/wk local only
Agent Visibility Check
by sadri-dridi

Is this website visible to AI agents? Robots, llms.txt, sitemap, extraction, then placement.

31 tools answering

Doorman — questions

Answers built from our own checks of this server.

What can Doorman do?
It exposes 3 tools, read directly from the server on our last check. Among them: doorman_check_ai_bot_access, doorman_check_robots_txt, doorman_write_robots_txt. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Doorman working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 17 of 17 checks got a reply (100.0%), average response time 84 ms. The bar chart above shows every period we have measured.
How do I connect Doorman?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Doorman need an API key?
No. Doorman completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Doorman?
It answers our handshake in 84 ms on average, which is faster than 93% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.