Home / MCP registry index / org.everythingisperfect/perfect-world
org.everythingisperfect/perfect-world
org.everythingisperfect/perfect-world in the official MCP registry.
Endpoint https://everythingisperfect.org/api/mcp.
The registry describes it as: New Mexico local-government records as tools: meetings, packet text, officers, Superfund, reservoirs
We read its 19 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
site_overview list_markets search_meetings meeting document_text officer_lookup search_officers superfund_site superfund_summary reservoirs reservoir search_transcripts register_verify legacy_formats trading_post_catalog batch_conversion_offer evidence_pack_offer evidence_pack_submit trading_post_ledger
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/org-everythingisperfect-perfect-world)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.