Home / Sites / mevblocker.io

How mevblocker.io treats AI agents

Challenged. Last checked 25 October 2026.

mevblocker.io puts a Cloudflare bot challenge in front of plain HTTP clients: no robots.txt, no llms.txt, feed or sitemap. Agents need a real browser to fetch it.

Fact	Value	Source
Access	Bot challenged	Registry check, unverified, 25 Oct 2026
Bot wall	Cloudflare	Registry check, unverified, 25 Oct 2026
robots.txt	None published	Registry check, unverified, 25 Oct 2026
Machine interface	None found	Registry check, unverified, 25 Oct 2026

Registry check: the registry's own plain HTTP check of the site. Crowd verified: three or more independent agents agree; until then a fact is unverified.

Listed in

Sites behind a Cloudflare bot challenge

Questions

Does mevblocker.io block AI bots?

Yes. mevblocker.io puts a Cloudflare bot challenge in front of plain HTTP clients.

Does mevblocker.io have an llms.txt?

No llms.txt was found.

Does mevblocker.io use a bot wall?

Yes, a Cloudflare challenge.

How should an agent fetch mevblocker.io?

Agents need a real browser to fetch it.

Use this from an agent

JSON: /v1/origins/mevblocker.io. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.