Model Context Protocol
Use OpenForBots checks from your AI assistant
The OpenForBots MCP server lets an assistant or coding agent that supports the Model Context Protocol call OpenForBots checks directly. It is read-only, needs no account, and returns the same evidence and limitations as the checks on this website.
Server address
Add this remote server to your MCP client. It uses the Streamable HTTP transport and does not require authentication.
https://openforbots.com/api/mcpConnect a client
Claude Code
claude mcp add --transport http openforbots https://openforbots.com/api/mcpOther MCP clients
Many clients accept a remote server entry similar to the following. Field names differ between clients, so check your client’s documentation for remote HTTP servers.
{
"mcpServers": {
"openforbots": {
"type": "http",
"url": "https://openforbots.com/api/mcp"
}
}
}Available tools
Reference and validation tools
These tools do not request any website.
validate_llms_txt- Validates llms.txt text supplied in the request, such as a draft before deployment, with the same rules as check_llms_txt. No website is fetched and the content is not stored.
lookup_ai_crawler- Looks up documented AI crawlers and data-use controls by robots.txt token, name, provider, or a full user-agent string, and returns purpose, robots.txt applicability, verification method, and the provider's documentation. Omit the query to list every record.
Website checks
These tools request public files from the website you name. Your client lists them only while live website checks are available on the server; if they are missing from your tool list, use the browser tools or the full audit instead.
audit_website- Fetches the public robots.txt, root llms.txt, and homepage of a website and returns evidence-backed findings with recommended actions, grouped by capability. Use it for an overall review. No aggregate score is produced.
check_robots_txt- Fetches a website's robots.txt and reports, for each documented AI crawler token, whether the root path is allowed or blocked and which rule matched. This is site-declared policy evidence; it does not show provider visits or enforcement.
check_llms_txt- Fetches the root /llms.txt file of a website and reports its response status, structure, links, and issues such as malformed, duplicate, or insecure links. Scoped files such as /docs/llms.txt are not requested.
Example requests
- “Does example.com block GPTBot or OAI-SearchBot in robots.txt?”
- “Validate this llms.txt draft before I deploy it.”
- “Which crawler sent this user agent, and how do I verify it?”
- “Audit example.com and list the findings with recommended actions.”
What the results show
Each result describes public files as they were observed at check time: robots.txt rules for documented crawler tokens, the root /llms.txt file, and the homepage HTML, structured data, and identity signals. Results include the evidence, a recommended action where one applies, and a link to open the full report on this website.
Results do not show whether any provider has crawled, indexed, retrieved, cited, ranked, recommended, or trained on a website. No aggregate score is produced. Crawler lookups come from the AI crawler reference, which documents provider-published information and does not certify crawlers.
Limits and privacy
- Each call checks one website. Only the hostname of a URL is used, and private or local hosts are rejected.
- Website checks request the homepage and the root
/llms.txtonly; other pages and scoped llms.txt files are not requested. - llms.txt content sent for validation is limited to 100 KB.
- OpenForBots does not save the websites, llms.txt content, or lookup text sent to the MCP server. Tool calls are counted by tool name and outcome only.
Last reviewed: .