Home / MCP registry index / org.directindex/scanner
org.directindex/scanner
org.directindex/scanner in the official MCP registry.
Endpoint https://directindex.org/mcp.
The registry describes it as: AI-agent readiness of business websites: scans, city indexes, assistants' answers, direct links.
We read its 20 tools on 2026-10-24. 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
scan_website get_site_report city_leaderboard find_direct_places menu_prices list_cities order_deep_report get_deep_report what_assistants_say assistant_recommendations assistant_destinations compare_cities country_summary rankings search_places direct_record vendor_report city_facts city_changes vendor_terms
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/org-directindex-scanner)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.