# My Privacy Agent MCP connector with account access

Endpoint: https://myprivacyagent.com/api/mcp

Transport: stateless Streamable HTTP over HTTPS. The full connector exposes 13 tools. Seven public reference tools work without an account: get_opt_out_instructions, list_opt_out_guides, get_removal_route, search_privacy_library, get_service_overview, get_route_verification, and get_library_verification_status.

Six account tools are available after OAuth sign-in: list_my_subjects, get_my_report, list_my_cases, get_case_status, request_recheck, and submit_approved_plan. Private calls without a valid token return an HTTP OAuth challenge so Claude can prompt for sign-in. Tokens must come from Clerk for this exact MCP endpoint; tokens for another resource are rejected.

Sign in with the account used for your existing verified check. Report and case access also requires a subject-specific share_results permission on https://myprivacyagent.com/connect. Each tool supplies the precise permission link when needed. Revoke individual permissions or the connected client at https://myprivacyagent.com/connect/manage.

request_recheck requires the separate run_check permission, an existing verified subject, Patrol entitlement, an earlier check and the 24-hour cooldown. It cannot start a first check or accept new personal details. submit_approved_plan requires submit_requests, existing website approval and paid entitlement. Without confirm:true it previews the plan; confirmation queues only already approved eligible requests. A request is not a removal. Neither tool buys a plan.

Private report responses omit personal identifiers, profile URLs and observed addresses. The website remains the place to inspect the complete report, approve listings, verify identity and buy optional services. This connector processes the signed-in person's account only. Public reference inputs must contain site names or domains, never personal identifiers.

Privacy: https://myprivacyagent.com/privacy
Support: support@myprivacyagent.com