Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.myprivacyagent/public

REMOTE · MYPRIVACYAGENT.COM

Read-only opt-out guides, removal routes for 950+ data brokers, and privacy library search.

0 this week 78 Trust /100

Last scanned (15 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Recent critical change

Authorization (28 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1554 tokens (~119/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 29% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 28 Oct 26 −1
    • Authorization: unverified → fail ▼ critical
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_service_overview” rewrote its description, which is the text the model reads security
    • Tool “list_my_cases” rewrote its description, which is the text the model reads security
    • Tool “list_my_subjects” rewrote its description, which is the text the model reads security
    • Tool “list_opt_out_guides” rewrote its description, which is the text the model reads security
    • Tool “search_privacy_library” rewrote its description, which is the text the model reads security
    • Tool “submit_approved_plan” rewrote its description, which is the text the model reads security
    • Tool “submit_approved_plan” is now declared destructive security
    • Schema quality: pass → fail ▼ functional
    • Tool “get_service_overview” changed its title: How to hand a person to My Privacy Agent → Read the My Privacy Agent service overview cosmetic
  • 23 Oct 26 79
    • The server rewrote its instructions, which are the text every model session reads security
  • 21 Oct 26 0
    • “get_opt_out_instructions” reworded the description of “broker” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

Diagnostics

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 Nov 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=YR1,O=Let's Encrypt,C=US 28 Sept 2026 27 Dec 2026 RSA 2048 SHA256-RSA 6c48e985d10cdeec6e0809ce273a127af3f
SANs: *.myprivacyagent.com, myprivacyagent.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 myprivacyagent.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
myprivacyagent.com. No DS 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
MCP tools · 13 exposed · ~1,001 tokens

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 →

Tool Tokens
get_case_status ~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.

NameTypeReqDescription
case_idstringyes–

No output schema declared.

No examples provided.

get_library_verification_status ~56

Read the actual catalog size, distinct route variants, current verified counts, checks captured today and the latest scheduled sweep. Counts include only native evidence that is still current; inventory rows, aliases and agent callbacks never count as verified.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_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.

NameTypeReqDescription
subject_idstring––

No output schema declared.

No examples provided.

get_opt_out_instructions ~113

The complete free website guide: direct answer, steps, troubleshooting, FAQs, official sources and content review date, plus separate current native verification. Retired sites return what-to-do-now guidance without historical actionable forms. Accepts a slug (spokeo), domain, name, alias, or URL. No login or personal lookup.

NameTypeReqDescription
brokerstringyesPublic site name, guide slug, domain, alias, broker URL, or canonical myprivacyagent.com/remove/<slug> URL. Never a person's details.

No output schema declared.

No examples provided.

get_removal_route ~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.

NameTypeReqDescription
domainstringyesDomain or URL on the site, e.g. spokeo.com or https://www.spokeo.com/...

No output schema declared.

No examples provided.

get_route_verification ~76

Read the exact official route variants for a domain or route ID, current independently checked scope, actor and region, capture time, expiry and failures. No badge means the route is not currently verified. This never starts a check or submits a request.

NameTypeReqDescription
routestringyesExact route ID, domain, or published guide slug.

No output schema declared.

No examples provided.

get_service_overview ~44

The public service description: tool scope, optional website pages for a private check, listing review and pricing, service limitations, and registry statistics. Contains public reference information only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_my_cases ~61

Requires OAuth and the 'share_results' permission. Lists removal cases with site, action, exact request status, verification status, human-only steps and dates. Filed, pending, needs review and verified removed are distinct states.

NameTypeReqDescription
subject_idstring––

No output schema declared.

No examples provided.

list_my_subjects ~54

Requires OAuth. Lists the person (first name, city, state, verification status) whose exposure this account has checked, with the subject_id used by account tools. Account setup and grant requirements are returned as structured statuses.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_opt_out_guides ~73

Summaries of every curated website guide and retired-site explanation, without duplicates. Includes kind, domain, category, documented method and content review date. Undocumented facts are null. Supports paging and category filters.

NameTypeReqDescription
categorystring––
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

request_recheck ~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.

NameTypeReqDescription
subject_idstring––

No output schema declared.

No examples provided.

search_privacy_library ~65

Search My Privacy Agent's published articles, opt-out guides, help answers, and plan facts about data brokers, opt-outs, relisting, pricing and service limitations. Returns ranked hits with canonical source URLs.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

submit_approved_plan ~108

Requires OAuth and the 'submit_requests' permission. Without confirm: true it previews eligible listings (status preview). With confirm: true it queues removal requests for exactly those listings using an existing website approval and paid entitlement. It cannot approve listings, pick new sites or buy anything; unmet requirements return approval_required or entitlement_required. A request is not a removal.

NameTypeReqDescription
confirmboolean–true only after the person has seen the preview and said yes.
subject_idstring––

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http com-myprivacyagent-public 'https://myprivacyagent.com/api/mcp'
Common questions

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 78 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 13 tools: get_opt_out_instructions, list_opt_out_guides, get_removal_route, search_privacy_library, get_service_overview, and 8 more. Their descriptions and schemas cost roughly 1,001 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.myprivacyagent/public MCP server?

VerifyMCP ran 13 checks on com.myprivacyagent/public, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.