A remote MCP server that checks whether a website will block an AI agent, and finds machine-friendly entry points such as llms.txt, MCP or OpenAPI.
What you can do
Check a single URL for agent access: fetch it as an AI agent and as a browser, detect bot challenges such as CAPTCHAs and bot walls, and read robots.txt rules for named AI crawlers and assistants. Find machine-friendly alternatives to scraping HTML, including llms.txt, well-known MCP and agent manifests, OpenAPI and plugin files. Batch-check up to 10 URLs in one call to pick usable sources. Show today's usage for a key or IP and the paid upgrade option.
When to use it
Useful when an assistant plans to browse, fetch or scrape a site and you want to know in advance whether it will be blocked, or when you want a structured feed or API instead of HTML scraping.
Requirements
Runs as a remote streamable HTTP endpoint; no package, environment variable or header is declared. The free tier is limited to 50 calls per day, and usage is tracked by key or IP.
Before you install
The server fetches the URLs you submit, so those addresses are sent to a third party. A paid upgrade is offered at $9 per month; the upgrade tool is described as not metered. Bot-detection results are a snapshot and may not match what your agent actually experiences.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.botrecipe%2Faccesscheck/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Before an agent browses or fetches a site, check if it will get in. Fetches the URL as an AI agent and as a browser, detects bot challenges (CAPTCHAs, DataDome, PerimeterX and other bot walls), reads robots.txt rules for GPTBot/ChatGPT-User/ClaudeBot/Claude-User/PerplexityBot and others, and looks for agent doors (llms.txt, MCP, OpenAPI). Returns verdict: open | challenged | blocked | robots_disallowed | unreachable, plus advice. Read-only. Use it before an automated web task, not for pages you already fetched successfully.
Parametersurlrequired
find_agent_alternative
Find a machine-friendly way into a site instead of scraping its HTML: llms.txt, /.well-known/mcp.json, agents.json, openapi.json, ai-plugin.json, and MCP URLs listed in llms.txt. Read-only.
Parametersurlrequired
check_many
Run check_agent_access on up to 10 URLs at once (counts as 1 call). Use it to pick which sources an agent can actually use.
Parametersurlsrequired
usage_and_upgrade
Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 50 calls/day. Not metered.
Takes no parameters.
Version history
2
v1.0.1LatestOct 15, 2026
v1.0.0Oct 15, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.