Home / MCP registry index / io.github.emmanuelorta/crawlcheck
CrawlCheck
io.github.emmanuelorta/crawlcheck in the official MCP registry.
Endpoint https://crawlcheck.io/mcp. Source: github.com/emmanuelorta/crawlcheck-core.
The registry describes it as: Verification layer for the agentic web: a signed answer about any site before an agent acts.
We read its 25 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
preflight best_source resolve_domain field_check scan_domain list_verified_capabilities mcp_servers verify_crawler_log corpus_state resolve_robots draft_llms fix_robots fix_entitymap video_check video_channel video_site registry_lookup crawler_path public_counts telemetry fix_mostly_code fix_stale_cache fix_machine_chain explain_finding machine_record
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-emmanuelorta-crawlcheck)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.