Home / MCP registry index / io.github.privatebydefault/default-privacy
Default Privacy
io.github.privatebydefault/default-privacy in the official MCP registry.
Endpoint https://mcp.defaultprivacy.com/.
The registry describes it as: Sourced privacy answers: how private an app is, tool picks, app swaps, de-Googling, breaches.
We read its 19 tools on 2026-10-26. 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
dp_search dp_search_tools dp_get_tool dp_list_categories dp_find_alternatives dp_how_private dp_get_related_tools dp_compare_tools dp_search_guides dp_get_guide dp_list_stacks dp_get_stack dp_route dp_check_mcp_server dp_search_glossary dp_get_glossary_term dp_check_email_security dp_check_whois_privacy dp_check_domain_breaches
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-privatebydefault-default-privacy)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.