com.myprivacyagent/public
REMOTE · MYPRIVACYAGENT.COM · SCANNED SEP 28
Read-only opt-out guides, removal routes for 950+ data brokers, and privacy library search.
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 11 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 Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1086 tokens (~98/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 23% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.myprivacyagent/public MCP server?
com.myprivacyagent/public is a hosted endpoint at https://myprivacyagent.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 · myprivacyagent.com
claude mcp add --transport http com-myprivacyagent-public 'https://myprivacyagent.com/api/mcp'
{
"mcpServers": {
"com-myprivacyagent-public": {
"url": "https://myprivacyagent.com/api/mcp"
}
}
} {
"servers": {
"com-myprivacyagent-public": {
"type": "http",
"url": "https://myprivacyagent.com/api/mcp"
}
}
} [mcp_servers.com-myprivacyagent-public] url = "https://myprivacyagent.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-myprivacyagent-public": {
"type": "remote",
"url": "https://myprivacyagent.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-myprivacyagent-public --url 'https://myprivacyagent.com/api/mcp' --transport streamable-http
mcp_servers:
com-myprivacyagent-public:
url: "https://myprivacyagent.com/api/mcp" {
"McpServers": {
"com-myprivacyagent-public": {
"Transport": "http",
"Url": "https://myprivacyagent.com/api/mcp"
}
}
} assistant mcp add com-myprivacyagent-public -t streamable-http -u 'https://myprivacyagent.com/api/mcp'
{
"mcpServers": {
"com-myprivacyagent-public": {
"type": "http",
"url": "https://myprivacyagent.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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Tool coverage: 29% → 23% ▼ functional
- Schema quality: 117 → 98 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: excellent → good functional
- New tool “get_case_status” functional
- New tool “get_my_report” functional
- New tool “list_my_cases” functional
- New tool “list_my_subjects” functional
- New tool “request_recheck” functional
- New tool “submit_approved_plan” functional
- 17 Sept 26 65
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 28 Sept 2026 · Probed https://myprivacyagent.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=*.myprivacyagent.com | CN=YR2,O=Let's Encrypt,C=US | 28 Jul 2026 | 26 Oct 2026 | RSA 2048 | SHA256-RSA | 68f6ef4544f6374608c4978b645c0927d20 |
| SANs: *.myprivacyagent.com, myprivacyagent.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 myprivacyagent.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| myprivacyagent.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://myprivacyagent.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://myprivacyagent.com/api/mcp | HTTPS enforced | 308 | https://myprivacyagent.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 →
get_case_status Read one removal case ~50
Requires OAuth and the 'share_results' permission. Returns one case by case_id with its current status, verification status, and any step only the person can do.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
No output schema declared.
No examples provided.
get_my_report Read my exposure report ~80
Requires OAuth and the 'share_results' permission for the subject. Returns the report summary the dashboard shows: status, counts, and per-site findings (site, status, what it exposes, guide link). No listing URLs or observed values are included. Returns authorization_required with a connect URL when the permission is missing.
| Name | Type | Req | Description |
|---|---|---|---|
| subject_id | string | – | – |
No output schema declared.
No examples provided.
get_opt_out_instructions Get opt-out instructions for a site ~105
Step-by-step, verified opt-out instructions for one people-search or data-broker site, plus what My Privacy Agent does for that site after a person authorizes it. Accepts a guide slug (spokeo), a domain (spokeo.com), an alias, or a URL on the site. Returns status not_found with a hint when no guide exists.
| Name | Type | Req | Description |
|---|---|---|---|
| broker | string | yes | Guide slug, domain, alias, or a URL on the broker's site. |
No output schema declared.
No examples provided.
get_removal_route Get the documented removal route for a site ~116
For any of the 950+ sites in the takedown registry: the documented removal method (form, email, both, guide, or none), the opt-out URL and privacy email on record, the parent company that actually processes the request, sibling sites one request may cover, and a link to our step-by-step guide when one exists. Accepts a domain or a URL.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain or URL on the site, e.g. spokeo.com or https://www.spokeo.com/... |
No output schema declared.
No examples provided.
get_service_overview How to hand a person to My Privacy Agent ~53
The public service description: scope of these tools, the private handoff pages (free check, review a listing, pricing), the rules assistants must follow, and registry statistics. Call this once before recommending the service.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_my_cases List my removal cases ~69
Requires OAuth and the 'share_results' permission. Lists removal cases (site, action, status, verification status, steps only the person can do, dates). Status words mean different things: filed, pending, needs review, verified removed. Never collapse them.
| Name | Type | Req | Description |
|---|---|---|---|
| subject_id | string | – | – |
No output schema declared.
No examples provided.
list_my_subjects List the subjects on my account ~56
Requires OAuth. Lists the person (first name, city, state, verification status) whose exposure this account has checked, with the subject_id other personal tools need. Returns authorization_required with a connect URL when the token is missing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_opt_out_guides List available opt-out guides ~72
Summaries of every published step-by-step guide (slug, domain, category, method, difficulty, turnaround, support level). Use it to find the right slug before calling get_opt_out_instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
request_recheck Re-check my exposure now ~105
Requires OAuth and the 'run_check' permission. Queues a fresh check of the person's existing details (the same re-scan Patrol runs monthly). Patrol plan only, verified subjects only, once per 24 hours; it never starts a first check and never takes new details. Returns queued, or a structured reason (not_allowed with retry_after, entitlement_required with pricing_url, unavailable, error). Purchases happen on the website only.
| Name | Type | Req | Description |
|---|---|---|---|
| subject_id | string | – | – |
No output schema declared.
No examples provided.
search_privacy_library Search the public privacy library ~79
Search My Privacy Agent's published articles, opt-out guides, help answers, and plan facts. Returns ranked hits with canonical URLs to cite. Use it before answering questions about data brokers, opt-outs, relisting, pricing, or what the service does and does not do.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
submit_approved_plan Queue the removal requests the person already approved ~137
Requires OAuth and the 'submit_requests' permission. Without confirm: true it only previews which eligible listings would be queued (status preview) — show that list to the person and get a yes first. With confirm: true it queues removal requests for exactly those listings, using the approval the person already gave on the website and their paid plan. It cannot approve listings, pick new sites, or buy anything: approval_required and entitlement_required send the person to the website. A request is not a removal.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | true only after the person has seen the preview and said yes. |
| subject_id | string | – | – |
No output schema declared.
No examples provided.
What is the com.myprivacyagent/public MCP server?
com.myprivacyagent/public is an MCP server listed in the public MCP registry as com.myprivacyagent/public. Read-only opt-out guides, removal routes for 950+ data brokers, and privacy library search. This page covers its hosted endpoint (https://myprivacyagent.com/api/mcp).
Is the com.myprivacyagent/public MCP server safe to use?
com.myprivacyagent/public scores 70 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 com.myprivacyagent/public MCP server expose?
com.myprivacyagent/public exposes 11 tools: get_opt_out_instructions, list_opt_out_guides, get_removal_route, search_privacy_library, get_service_overview, and 6 more. Their descriptions and schemas cost roughly 922 tokens of context every time the server is loaded.
Does the com.myprivacyagent/public MCP server require authentication?
No. We connected to com.myprivacyagent/public without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.myprivacyagent/public MCP server still maintained?
com.myprivacyagent/public is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.