Local MCP capabilities provider for Expo
Nothing to run from here
Default Privacy is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Search privacy tools, guides, stacks and glossary, find app replacements, run privacy checks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http default-privacy-mcp https://mcp.defaultprivacy.com
# 2 — ask your agent for something these tools do
# dp_search, dp_search_tools, dp_get_tool and 15 more
Default Privacy costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PRAll 1 server
privatebydefault1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http default-privacy-mcp https://mcp.defaultprivacy.comReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Start here for a general privacy question. One keyword search across the whole hub: directory tools, how-to guides, curated tool stacks and the glossary. Use 1–3 keywords such as 'vpn', 'data broker' or 'grapheneos'; every keyword must match, and filler words like 'how', 'best' and 'private' are ignored. Returns the top few results of each type, each with type, title, slug, a one-line summary and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | 1–3 keywords, e.g. 'vpn', 'data broker', 'tor', 'grapheneos'. |
| limit | integer | no | Max results per type (1–10, default 3). |
Use when a user wants privacy tool recommendations (VPNs, email, browsers, messengers, password managers, etc.). Matches records containing every query word, so 1–2 keywords such as 'vpn' or 'password manager' work and a full sentence usually returns nothing. For a whole kind of tool, use category instead (slugs from dp_list_categories). Put requirements in the filters. Returns 10 records by def
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | 1–2 keywords matched against name, tagline, and description; every word must match. E.g. 'vpn', 'email', 'notes'. |
| category | string | no | Category slug or name to filter by (see dp_list_categories). |
| open_source | boolean | no | Only open-source tools. |
| e2ee | boolean | no | Only end-to-end encrypted tools. |
| has_free_tier | boolean | no | Only tools with a free tier. |
| sort | string | no | Sort order. Default 'picks': DP picks first, then A to Z. 'ado_score' is a deprecated alias of 'picks'. |
| limit | integer | no | Max results (1–50, default 10). |
| offset | integer | no | Pagination offset (default 0). |
Fetch one directory tool's full record by slug: description, DP pick (if any), jurisdiction, encryption, PII requirements, platforms, and its Default Privacy page (dp_url). Also returns sources (links, keyed by the field they back, with the date checked) and caveats (things to know before choosing). A null field means Default Privacy has not checked it (never read null as no); quote the caveat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Tool slug, e.g. 'proton', 'signal', 'mullvad'. |
List the privacy tool directory's category groups and subcategories with tool counts. Use the returned slugs to filter dp_search_tools.
No parameter schema on file.
Use when a user wants to replace a mainstream product: consumer apps and services (Gmail, WhatsApp, Chrome, Google Drive, Zoom, LastPass, Windows…) or a website tracker / ad script (Google Analytics, Hotjar, Mixpanel, Facebook Pixel…). Pass the product's name. Trackers return a curated swap list. Consumer products return a hand-picked list of directory tools that replace them (DP picks first, then
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | The product to replace, by name, e.g. 'WhatsApp', 'Gmail', 'Google Analytics'. |
| limit | integer | no | Max alternatives (default 8). |
Use after dp_get_tool for 'what else is like X?': returns other tools in the same directory category with DP picks first, then A to Z, excluding X. X must be a directory slug; for a product the directory doesn't list, use dp_find_alternatives.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Tool slug to find peers for, e.g. 'signal'. |
| limit | integer | no | Max related tools (default 5). |
Fetch the full Privacy Protocol records for 2–5 tools by slug for side-by-side comparison (DP pick, jurisdiction, encryption, PII requirements), each with sources and caveats. A null field means Default Privacy has not checked it (never read null as no); quote the caveats and cite the sources. Use to help a user choose between shortlisted tools.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slugs | array | yes | 2–5 tool slugs to compare, e.g. ['signal','simplex-chat']. |
Search Default Privacy's long-form privacy how-tos, e.g. switching to GrapheneOS, keeping a home address off people-search sites, data-broker removal, running your own VPN, and the 'How to Live Privately' series. Filter by category. Returns metadata and links; use dp_get_guide for full content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | 1–3 keywords matched as whole words against title, tags, and description; every keyword must match. Best match first. |
| category | string | no | Filter by guide category (e.g. Privacy, Financial Privacy, Self-Hosting). |
| limit | integer | no | Max results (default 20). |
Fetch a single guide's full markdown content and metadata by slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Guide slug, e.g. 'remove-name-from-data-brokers'. |
List every privacy stack: a curated set of directory tools for one goal or threat (a privacy starter kit, de-Googling, leaving Gmail, a journalist's or a stalking survivor's kit, Windows hardening…). Returns title, slug, a short description and url for each; use dp_get_stack for one stack's full content.
No parameter schema on file.
Fetch one privacy stack's full markdown content and metadata by slug: the tools in setup order, why each one, and the tradeoffs. Slugs come from dp_list_stacks or dp_search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Stack slug, e.g. 'privacy-starter-kit', 'degoogle-android-phone'. |
Describe the user's situation or goal in their own words (e.g. "I'm a journalist protecting sources", "I just bought a Pixel and want GrapheneOS", "which password manager", "I want to use AI more privately") and get the best-matching Default Privacy situations, each with the guides and stacks to read. The standard starting set is always included. Open a result with dp_get_guide or dp_get_stack. Fo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| situation | string | yes | The situation or goal, in the user's own words. |
Before connecting an MCP server, check whether it is in Default Privacy's vetted list and what it can read or change. Give its repository URL, server URL, name or slug. A listed server returns its record with sources and caveats. An unlisted one returns a short checklist plus, for a GitHub or registry name, what the publisher declared in the official MCP registry (not a review); unlisted is not a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| server | string | yes | The server's repository URL, server URL, name or slug, e.g. 'https://github.com/bitwarden/mcp-server'. |
Search the privacy & security glossary for defined terms. Returns term, definition, and link; use dp_get_glossary_term for the full entry.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Term or keyword to search for, e.g. 'metadata', 'tor'. |
| limit | integer | no | Max results (default 25). |
Fetch a single glossary term's full definition and content by slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Glossary term slug, e.g. 'end-to-end-encryption'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. 'example.com'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. 'example.com'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. 'example.com'. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Default Privacy or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.6.0.
1.6.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Default Privacy can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.