Default Privacy
Search vetted privacy tools, read guides & glossary, and run free privacy diagnostics.
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Search vetted privacy tools, read guides & glossary, and run free privacy diagnostics.
How to connect
How to connect Default Privacy to Claude
The server address to paste into Claude settings:
https://defaultprivacy.com/api/mcp
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Default Privacy to ChatGPT
The server address to paste into ChatGPT settings:
https://defaultprivacy.com/api/mcp
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Default Privacy to Cursor
The server address to paste into Cursor settings:
https://defaultprivacy.com/api/mcp
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (14)
Raw names from tools/list. Only developers need these.
| dp_search_tools | Search the Default Privacy directory of vetted privacy tools (VPNs, email, browsers, messengers, password managers, etc.). Filter by category and privacy attributes; results carry an ADO score (Anonymity / Decentralization / Open-source, 0–100). Prefer higher ADO when recommending. |
| dp_get_tool | Fetch a single privacy tool's full Privacy Protocol record by slug — description, ADO score, jurisdiction, encryption, PII requirements, platforms, and audit status. |
| dp_list_categories | List the privacy tool directory's category groups and subcategories with tool counts. Use the returned slugs to filter dp_search_tools. |
| dp_find_alternatives | Given a mainstream or privacy-hostile product/service (e.g. 'Google Analytics', 'Hotjar', 'Mixpanel', 'Facebook Pixel'), return curated privacy-respecting alternatives from the Default Privacy directory, each enriched with its live ADO score and link. Use when a user wants to replace a tracking or privacy-hostile tool. |
| dp_get_related_tools | Given a directory tool slug, return other tools in the SAME category ranked by ADO score — a shortlist of peers/alternatives within the directory. Excludes the input tool. |
| dp_compare_tools | Fetch the full Privacy Protocol records for 2–5 tools by slug for side-by-side comparison (ADO score, jurisdiction, encryption, PII requirements, audit status). Use to help a user choose between shortlisted tools. |
| dp_search_guides | Search Default Privacy's long-form guides and playbooks. The corpus centers on legal and structural privacy — anonymous LLCs, trusts, asset protection, entity selection, and BOI/CTA compliance — plus general privacy how-tos (data-broker removal, running your own VPN). Filter by category. Returns metadata and links; use dp_get_guide for full content. |
| dp_get_guide | Fetch a single guide's full markdown content and metadata by slug. |
| dp_search_glossary | Search the privacy & security glossary for defined terms. Returns term, definition, and link; use dp_get_glossary_term for the full entry. |
| dp_get_glossary_term | Fetch a single glossary term's full definition and content by slug. |
| dp_check_email_security | Check a domain's email authentication posture — SPF, DKIM, and DMARC DNS records — and return an A–F grade with explanations. Read-only DNS lookups; no email is sent or stored. |
| dp_check_whois_privacy | Look up a domain's public WHOIS/RDAP registration record and flag exposed personal identity fields (registrant name, email, phone, address). Read-only RDAP lookup. |
| dp_check_domain_breaches | Check whether a domain appears in known public data breaches (via the Have I Been Pwned breach catalog). Returns matching breaches with dates, exposed data classes, and account counts. Domain-level only — no personal email is queried. |
| dp_check_password_pwned | Check whether a password has appeared in known breaches using HIBP k-anonymity. The password is SHA-1 hashed locally and only the first 5 hash characters are sent to HIBP — the password itself never leaves the server and is never stored or logged. Returns whether it was found and how many times. |