Default Privacy
REMOTE · DEFAULTPRIVACY.COM · SCANNED SEP 21
Search vetted privacy tools, read guides & glossary, and run free privacy diagnostics.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1585 tokens (~88/item across 18 items; 14 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Default Privacy MCP server?
Default Privacy is a hosted endpoint at https://defaultprivacy.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · defaultprivacy.com
claude mcp add --transport http privatebydefault-default-privacy 'https://defaultprivacy.com/api/mcp'
{
"mcpServers": {
"privatebydefault-default-privacy": {
"url": "https://defaultprivacy.com/api/mcp"
}
}
} {
"servers": {
"privatebydefault-default-privacy": {
"type": "http",
"url": "https://defaultprivacy.com/api/mcp"
}
}
} [mcp_servers.privatebydefault-default-privacy] url = "https://defaultprivacy.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"privatebydefault-default-privacy": {
"type": "remote",
"url": "https://defaultprivacy.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add privatebydefault-default-privacy --url 'https://defaultprivacy.com/api/mcp' --transport streamable-http
mcp_servers:
privatebydefault-default-privacy:
url: "https://defaultprivacy.com/api/mcp" {
"McpServers": {
"privatebydefault-default-privacy": {
"Transport": "http",
"Url": "https://defaultprivacy.com/api/mcp"
}
}
} assistant mcp add privatebydefault-default-privacy -t streamable-http -u 'https://defaultprivacy.com/api/mcp'
{
"mcpServers": {
"privatebydefault-default-privacy": {
"type": "http",
"url": "https://defaultprivacy.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://defaultprivacy.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=defaultprivacy.com | CN=YR1,O=Let's Encrypt,C=US | 20 Jul 2026 | 18 Oct 2026 | RSA 2048 | SHA256-RSA | 56204ea3a089f7f1a25e02b06f70b47d9e3 |
| SANs: defaultprivacy.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of defaultprivacy.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| defaultprivacy.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://defaultprivacy.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://defaultprivacy.com/api/mcp | HTTPS enforced | 308 | https://defaultprivacy.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dp_check_domain_breaches Check domain data breaches ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. 'example.com'. |
No output schema declared.
No examples provided.
dp_check_email_security Check email security (SPF/DKIM/DMARC) ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. 'example.com'. |
No output schema declared.
No examples provided.
dp_check_password_pwned Check if a password is breached ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| password | string | yes | Password to check. Handled via k-anonymity; never transmitted in full or stored. |
No output schema declared.
No examples provided.
dp_check_whois_privacy Check WHOIS / domain privacy ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. 'example.com'. |
No output schema declared.
No examples provided.
dp_compare_tools Compare privacy tools ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | 2–5 tool slugs to compare, e.g. ['signal','simplex-chat']. |
No output schema declared.
No examples provided.
dp_find_alternatives Find privacy alternatives to a product ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max alternatives (default 8). |
| product | string | yes | The product/service to replace, e.g. 'Google Analytics', 'Hotjar'. |
No output schema declared.
No examples provided.
dp_get_glossary_term Get one glossary term ~46
Fetch a single glossary term's full definition and content by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Glossary term slug, e.g. 'end-to-end-encryption'. |
No output schema declared.
No examples provided.
dp_get_guide Get one guide ~44
Fetch a single guide's full markdown content and metadata by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Guide slug, e.g. 'anonymous-llc-wyoming'. |
No output schema declared.
No examples provided.
dp_get_related_tools Get related tools (same category) ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max related tools (default 5). |
| slug | string | yes | Tool slug to find peers for, e.g. 'signal'. |
No output schema declared.
No examples provided.
dp_get_tool Get one privacy tool ~66
Fetch a single privacy tool's full Privacy Protocol record by slug — description, ADO score, jurisdiction, encryption, PII requirements, platforms, and audit status.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Tool slug, e.g. 'proton', 'signal', 'mullvad'. |
No output schema declared.
No examples provided.
dp_list_categories List directory categories ~35
List the privacy tool directory's category groups and subcategories with tool counts. Use the returned slugs to filter dp_search_tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dp_search_glossary Search glossary ~76
Search the privacy & security glossary for defined terms. Returns term, definition, and link; use dp_get_glossary_term for the full entry.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 25). |
| query | string | – | Term or keyword to search for, e.g. 'metadata', 'tor'. |
No output schema declared.
No examples provided.
dp_search_guides Search guides ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by guide category (e.g. Formation, Legal, Compliance, Tax, Structure, Financial Privacy, Privacy, Self-Hosting). |
| limit | integer | – | Max results (default 20). |
| query | string | – | Free-text search over guide title, description, and tags. |
No output schema declared.
No examples provided.
dp_search_tools Search privacy tools ~259
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accepts_crypto | boolean | – | Only tools that accept cryptocurrency. |
| category | string | – | Category slug or name to filter by (see dp_list_categories). |
| e2ee | boolean | – | Only end-to-end encrypted tools. |
| has_free_tier | boolean | – | Only tools with a free tier. |
| limit | integer | – | Max results (1–50, default 10). |
| min_ado_score | number | – | Minimum ADO composite score (0–100). |
| no_kyc | boolean | – | Only tools that require no KYC to purchase/use. |
| offset | integer | – | Pagination offset (default 0). |
| open_source | boolean | – | Only open-source tools. |
| query | string | – | Free-text search over tool name and tagline, e.g. 'vpn', 'email', 'notes'. |
| sort | string | – | Sort order. Defaults to highest ADO score first. |
No output schema declared.
No examples provided.
What is the Default Privacy MCP server?
Default Privacy is an MCP server listed in the public MCP registry as io.github.privatebydefault/default-privacy. Search vetted privacy tools, read guides & glossary, and run free privacy diagnostics. This page covers its hosted endpoint (https://defaultprivacy.com/api/mcp).
Is the Default Privacy MCP server safe to use?
Default Privacy scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Default Privacy MCP server expose?
Default Privacy exposes 14 tools: dp_search_tools, dp_get_tool, dp_list_categories, dp_find_alternatives, dp_get_related_tools, and 9 more. Their descriptions and schemas cost roughly 1,259 tokens of context every time the server is loaded.
Does the Default Privacy MCP server require authentication?
No. We connected to Default Privacy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Default Privacy MCP server still maintained?
Default Privacy is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.