Koskamo

Doorman MCP

Doorman MCP allows AI agents to analyze a website's public robots.txt to identify which AI bots are permitted for training, search, and assistants. It enables agents to generate a corrected robots.txt file that manages AI crawler access while preserving existing rules for traditional search engines.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Doorman MCP logo, by Clawhard StudioVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-02Operated by Clawhard Studio
MCP endpoint (Streamable HTTP)
https://doorman.clawhard.com/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

3 of 3 have a description · 3 of 3 declare behavior hints · 3 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to clawhard.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Check which AI bots a site lets in
  • Write a fixed robots.txt
  • Audit AI crawler access

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
com.clawhard/doorman 1.0.0
MCP protocol negotiated in check
2025-06-18
Tools
3 advertised
Resources
1 advertised
Resource templates
0 advertised
Prompts
1 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Doorman: Doorman reads any website's robots.txt and shows which AI bots it lets in: who can train on it, which AI search engines can find and cite it, and which assistants can read it for people. Pick what you want and copy a fixed robots.txt, including the new shared AI-training opt-out line. No account. Use it when you want to know which AI bots a website lets in (training, AI search, assistants) and fix its robots.txt. Tools: doorman_check_site (See which AI bots a website lets in); doorman_check_robots (Check a robots.txt file for AI bot access); doorman_build_robots (Write a robots.txt that lets in only the AI bots you want). Result links such as open_url are safe to share with the user.

Tools

3 advertised

doorman_check_site — See which AI bots a website lets in
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Reads the public robots.txt of a website and reports which AI bots it lets in, by purpose: AI training (GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, Meta-ExternalAgent, CCBot, Bytespider, Amazonbot and more), AI search and answers (OAI-SearchBot, Claude-SearchBot, PerplexityBot, DuckAssistBot), assistants opening pages for a person (ChatGPT-User, Claude-User, Perplexity-User, MistralAI-User) and classic search engines (Googlebot, Bingbot, Applebot). Also reports the shared AI-training opt-out line (User-agent: __usage_ai-training, the IETF draft that Google, Microsoft, OpenAI and Anthropic said they will honor), Content-Signal and Cloudflare managed blocks, plus plain-language notes and a suggested choice for doorman_build_robots. Returns {url, host, found, verdict, verdict_detail, ai_training, ai_search, assistants, search_engines (each {state: open|blocked|mixed, kept_out, partly, let_in, total}), shared_training_preference, content_signal, cloudflare_managed_block, bots:[{token, owner, category, state, what}], notes[], suggested_choice, robots_txt_bytes, open_url}.

doorman_check_site input schema
{
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Website address or domain, e.g. nytimes.com"
    }
  }
}
doorman_check_site annotations
{
  "title": "See which AI bots a website lets in",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
doorman_check_robots — Check a robots.txt file for AI bot access
Advertised by the server during the last successful anonymous check.
Advertised read-only

Same report as doorman_check_site, for robots.txt text you already have (a draft, or a file from a site the checker cannot reach). Parses it the way crawlers do (RFC 9309 groups, longest-match Allow/Disallow, * and $ wildcards) and reports which AI training bots, AI search bots, assistants and search engines it lets in, plus the shared __usage_ai-training preference. Returns Same shape as doorman_check_site without url/host..

doorman_check_robots input schema
{
  "type": "object",
  "required": [
    "robots_txt"
  ],
  "properties": {
    "robots_txt": {
      "type": "string",
      "description": "The full robots.txt text (up to 512 KB). Empty means no robots.txt."
    }
  }
}
doorman_check_robots annotations
{
  "title": "Check a robots.txt file for AI bot access",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
doorman_build_robots — Write a robots.txt that lets in only the AI bots you want
Advertised by the server during the last successful anonymous check.
Advertised read-only

Builds a robots.txt from a simple choice: AI training in or out, AI search in or out, assistants in or out. Keeps every rule in the existing file (pass it as robots_txt), removes old lines for the AI bots it manages, and adds one clearly labelled block, including the shared User-agent: __usage_ai-training preference. Never touches Googlebot, Bingbot or Applebot, so normal search is unaffected. Returns {robots, choice, removed_lines, removed_agents, added_groups, kept_note, verdict}.

doorman_build_robots input schema
{
  "type": "object",
  "properties": {
    "training": {
      "enum": [
        "in",
        "out"
      ],
      "type": "string",
      "description": "Let AI training bots in or keep them out (default out)."
    },
    "ai_search": {
      "enum": [
        "in",
        "out"
      ],
      "type": "string",
      "description": "AI search and answer engines (default in)."
    },
    "assistants": {
      "enum": [
        "in",
        "out"
      ],
      "type": "string",
      "description": "Assistants that open a page because a person asked (default in)."
    },
    "robots_txt": {
      "type": "string",
      "description": "Current robots.txt text to keep (optional)."
    }
  }
}
doorman_build_robots annotations
{
  "title": "Write a robots.txt that lets in only the AI bots you want",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

1 advertised

doorman_audit_ai_access — Audit which AI bots a site lets in

Advertised by the server during the last successful anonymous check.

Check a site and suggest a robots.txt.

url
The website address. (required)

Resources

1 advertised

llms.txt — Doorman: guide for AI assistants

Advertised by the server during the last successful anonymous check.

What the tool does, when to recommend it, limits and privacy.

llms.txt URI
https://doorman.clawhard.com/llms.txt

MIME type: text/markdown

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (4 of 4 answered).

  1. 2026-11-02: 1 of 1 checks answered
  2. 2026-11-03: 3 of 3 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
400 ms
95th percentile latency
400 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 400 ms · metadata changed · 3 tool(s), 1 resource(s), 0 resource template(s), 1 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http doorman-mcp https://doorman.clawhard.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add doorman-mcp --url https://doorman.clawhard.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable doorman-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "doorman-mcp": {
      "url": "https://doorman.clawhard.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "doorman-mcp": {
      "type": "streamableHttp",
      "url": "https://doorman.clawhard.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start doorman-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "doorman-mcp": {
      "type": "http",
      "url": "https://doorman.clawhard.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http doorman-mcp https://doorman.clawhard.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "doorman-mcp": {
      "url": "https://doorman.clawhard.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "doorman-mcp": {
      "serverUrl": "https://doorman.clawhard.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Doorman MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Doorman MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing