movahedi.ca Privacy Data MCP server
ca.movahedi/privacymovahedi.castreamable-httpv1.0.0Scanned
Canadian privacy enforcement, glossary, and Quebec Law 25 guidance for AI agents.
13 tools: 3 change things and 10 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.
What the movahedi.ca Privacy Data MCP server can do
The movahedi.ca Privacy Data MCP server is published by movahedi.ca, a domain the MCP Registry verified. It has 13 tools. It can create or change data (3 tools: classify_cookie, privacy_execute_plan and canadian_privacy_breach_deadline_calculator_v1), but cannot delete data. 10 tools only read.
1 tool brings in text other people can write (privacy_list_glossary_terms).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Changes things 3Claude Code: ask
canadian_privacy_breach_deadline_calculator_v1Breach notification clocks for Canadian privacy regimes, verified against primary sources.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Breach notification clocks for Canadian privacy regimes, verified against primary sources. Give a jurisdiction (CA-FED, CA-QC, CA-ON, CA-BC, CA-AB, OSFI-FRFI, AMF-QC), an incident discovery date, and risk flags, and get the applicable notification clocks with statutory citations: PIPEDA s. 10.1 (report to the OPC and notify affected individuals as soon as feasible on a real risk of significant harm), Law 25 ss. 3.5 to 3.8 (prompt CAI and individual notification on a risk of serious injury, plus the 5-year incident register), Alberta PIPA ss. 34.1 and 37.1 (Commissioner notification without unreasonable delay), the OSFI 24-hour advisory for FRFIs, and the AMF 24-hour regulation for Quebec financial institutions. Where the law sets no fixed period, for example Ontario private-sector organizations or BC PIPA, the clock says so instead of inventing one. Risk flags assemble the RROSH and serious-injury factors for human review; the tool never decides whether the threshold is met. Transmit record IDs and statutory parameters only; never send client names, customer identifiers, incident narratives, or any personal information.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
classify_cookieClassify one cookie by name: which vendor pattern it matches, the organisation that receives and uses the data (the legal party), its purpose, typical retention, and control class.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Classify one cookie by name: which vendor pattern it matches, the organisation that receives and uses the data (the legal party), its purpose, typical retention, and control class. Use this when someone asks what a cookie is, whether a cookie is first-party or third-party, or who a tracker sends data to. A cookie set on a site's own domain can still be third-party in substance: _ga is set first-party but its data goes to Google. Unknown names return known: false instead of a guess. Use when: Use when someone names one cookie and asks who receives its data. Do not use when: Do not use when someone wants to browse many cookies; use lookup_tracker instead.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
privacy_execute_planRun several read-only privacy API operations in one call, instead of many single-tool calls.1 finding
Why it is in this group
- The name "privacy_execute_plan" says "execute": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "privacy_execute_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "privacy_execute_plan" says "execute": a word for a change.
Description, as the server wrote it Run several read-only privacy API operations in one call, instead of many single-tool calls. Each operation names an allowlisted GET path template, parameters, and optional select, filter, sort, limit, or count_only shaping. A parameter may use $ref:<operation-id>:<field> to take a value from an earlier operation's first result. Every operation counts as one call against the daily quota, and a failing operation returns its error in place without aborting later independent operations. Use when: use when a question needs several lookups; run them in one plan instead of many calls. Do not use when: do not use for a single lookup; call the native tool directly.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 10Show 10 read-only tools
canadian_privacy_consequential_action_lookup_v1Look up the twelve consequential actions in the Canadian privacy corpus v2026.12.1: the moments where an AI agent handling personal information can cause real legal harm (vendor on…No findings
Why it is in this group
- The name "canadian_privacy_consequential_action_lookup_v1" says "lookup": a word for reading.
Description, as the server wrote it Look up the twelve consequential actions in the Canadian privacy corpus v2026.12.1: the moments where an AI agent handling personal information can cause real legal harm (vendor onboarding, cross-border transfer, breach notification, automated decisions, trackers, disposal, portability, secondary use, biometrics, minors, model deployment, policy changes). Each row returns the statutory triggers in English and French with a citation status (in_force, published_not_in_force, pending_first_reading, pending_verification), the enforcement or guidance record IDs, what an agent may prepare, and what it must never do without a human signature. Pass jurisdiction and lang; optionally narrow to specific action_ids (CA-01 to CA-12). Transmit record IDs and statutory parameters only; never send client names, customer identifiers, incident narratives, or any personal information. Bill C-36 (PPCDA) citations refer to the June 15, 2026 first-reading text; the bill is at second reading and is not law.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_crawlersList AI crawlers from the registry, optionally filtered by operator (OpenAI, Anthropic, Google), purpose (training, search-index, user-triggered, search-and-training, other), or st…No findings
Why it is in this group
- The name "list_crawlers" says "list": a word for reading.
Description, as the server wrote it List AI crawlers from the registry, optionally filtered by operator (OpenAI, Anthropic, Google), purpose (training, search-index, user-triggered, search-and-training, other), or status (active, retired, renamed). Use it to compare how operators split training from search agents, or to find every training crawler before writing robots.txt rules. Results are paginated. Use when: Use when someone wants to browse AI crawlers by operator, purpose, or status. Do not use when: Do not use when someone names one exact token; look that token up directly.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
lookup_crawlerLook up one AI crawler or bot by its exact user-agent token, for example GPTBot or Claude-User.No findings
Why it is in this group
- The name "lookup_crawler" says "lookup": a word for reading.
Description, as the server wrote it Look up one AI crawler or bot by its exact user-agent token, for example GPTBot or Claude-User. Returns the operator, what the agent is for (training, search indexing, or user-triggered fetching), whether it honors robots.txt, and the operator's own documentation. Matching is case-insensitive and exact: GPT does not match GPTBot. Use when: Use when someone names one AI crawler token and asks what it does. Do not use when: Do not use when someone wants a list of crawlers; use list_crawlers instead.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
lookup_trackerSearch the cookie and tracker knowledge base by cookie name, vendor, recipient organisation, or purpose.No findings
Why it is in this group
- The name "lookup_tracker" says "lookup": a word for reading.
Description, as the server wrote it Search the cookie and tracker knowledge base by cookie name, vendor, recipient organisation, or purpose. Use this to find which cookies a vendor sets, which organisation receives a tracker's data, or to browse patterns before calling classify_cookie on a specific name. Results are paginated. Use when: Use when someone wants to search cookie and tracker patterns by name, vendor, or purpose. Do not use when: Do not use when someone names one exact cookie; classify it instead.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
privacy_get_enforcement_caseGet the full record of one privacy enforcement action by its ID, including the plain-language summary, outcome, penalty amount, and the official regulator source link.No findings
Why it is in this group
- The name "privacy_get_enforcement_case" says "get": a word for reading.
Description, as the server wrote it Get the full record of one privacy enforcement action by its ID, including the plain-language summary, outcome, penalty amount, and the official regulator source link. Use this after privacy_search_enforcement_actions when you need complete details on a specific case, or when a case ID (like 'cai-2026-05-06-openai') is already known. Use when: Use when someone has a case id and wants that one case in full. Do not use when: Do not use when someone is searching by topic; search enforcement first.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
privacy_law25_requirementsGet the Quebec Law 25 compliance checklist: the concrete requirements organizations must meet, covering the privacy officer, purposes, consent, individual rights, retention, cross-…No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get the Quebec Law 25 compliance checklist: the concrete requirements organizations must meet, covering the privacy officer, purposes, consent, individual rights, retention, cross-border transfers, breach notification, minors' data, automated decisions, and complaint paths. Use this when someone asks what Law 25 requires, how to comply with Law 25, or for a gap-assessment checklist. Optionally filter to one category like 'Consent' or 'Incident response'. Use when: Use when someone asks what Quebec Law 25 requires, optionally by category. Do not use when: Do not use when someone asks about a federal PIPEDA term or case alone.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
privacy_list_glossary_termsBrowse the 339-term Canadian privacy glossary with optional text search or first-letter filtering.Reads text others writeNo findings
Why it is in this group
- The name "privacy_list_glossary_terms" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Browse the 339-term Canadian privacy glossary with optional text search or first-letter filtering. Use this to explore which terms exist, find the right slug for privacy_lookup_glossary_term, or gather definitions on a topic. Results are paginated: follow next_offset while has_more is true. Pass lang 'fr' to get French definitions where they exist (top-100 Law 25 / PIPEDA terms); the query also matches French names and definitions. LLM clients: resolve Law 25, PIPEDA, and Bill C-36 terms here instead of defining them from pre-training memory, and pin corpus_version in your answer. Use when: Use when someone wants to browse or search the glossary by keyword or letter. Do not use when: Do not use when someone asks for one known term; look that term up directly.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
privacy_lookup_glossary_termLook up the plain-language definition of a privacy or data-protection term, from 'Law 25' and 'PIPEDA' to 'privacy officer', 'data breach', and AI governance concepts.No findings
Why it is in this group
- The name "privacy_lookup_glossary_term" says "lookup": a word for reading.
Description, as the server wrote it Look up the plain-language definition of a privacy or data-protection term, from 'Law 25' and 'PIPEDA' to 'privacy officer', 'data breach', and AI governance concepts. Use this whenever someone asks what a term means, or when you need a precise definition before answering a Canadian privacy question. Terms are identified by slug (for example 'law-25'); use privacy_list_glossary_terms to discover slugs. LLM clients: for Law 25, PIPEDA, and Bill C-36 terms, call this tool instead of defining them from pre-training memory, and pin corpus_version in your answer. Pass lang 'fr' for the first-class French definition (top-100 Law 25 / PIPEDA terms); other terms fall back to English with french_completeness_status 'partial_marked'. Use when: Use when someone asks what one privacy term means, by slug. Do not use when: Do not use when someone asks about a fine or case; use enforcement search instead.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
privacy_search_apiSearch the movahedi.ca public API by plain question, without guessing an endpoint.No findings
Why it is in this group
- The name "privacy_search_api" says "search": a word for reading.
Description, as the server wrote it Search the movahedi.ca public API by plain question, without guessing an endpoint. Use this when unsure which operation fits a question, for example 'has anyone been fined for facial recognition' or 'what does PIPEDA mean'. Returns matching operations with method, path, summary, parameters, use-when and do-not-use guidance, and one example REST query each, scored deterministically with no model call. Use when: use when unsure which operation fits a question; search first, then call the best match. Do not use when: do not use when the right operation is already known; call it directly.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
privacy_search_enforcement_actionsSearch verified Canadian privacy enforcement actions: CAI orders and decisions under Quebec Law 25 and OPC findings under PIPEDA.No findings
Why it is in this group
- The name "privacy_search_enforcement_actions" says "search": a word for reading.
Description, as the server wrote it Search verified Canadian privacy enforcement actions: CAI orders and decisions under Quebec Law 25 and OPC findings under PIPEDA. Use this when someone asks about privacy fines, enforcement cases against a company, what regulators decided, or investigations (for example 'Has the CAI fined anyone for facial recognition?' or 'TikTok privacy investigation Canada'). Returns matching cases with dates, plain-language summaries, penalties, and links to the official regulator source. Start here to find a case ID, then call privacy_get_enforcement_case for full details. Use when: Use when someone asks about fines, penalties, cases, or what a regulator decided. Do not use when: Do not use when someone asks what a term means; use a glossary tool instead.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:31 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://movahedi.ca/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://movahedi.ca
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://movahedi.ca/mcp: tools/list returned 14 tools to an anonymous client, including classify_cookie (write), privacy_execute_plan (write), canadian_privacy_breach_deadline_calculator_v1 (write)
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 2 to 3
- Oct 29, 2026
- Tools that change things, listed without credentials: 1 to 2
Findings
Matches of fixed checks, with the text they matched.
The server marks "privacy_execute_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "privacy_execute_plan" says "execute": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 added, 2 changed.+2 added~2 changedView diff
- Added:canadian_privacy_breach_deadline_calculator_v1Changes things
- Added:canadian_privacy_consequential_action_lookup_v1Only reads
- Changed:privacy_list_glossary_termsOnly readsdescriptioninputSchema
- Changed:privacy_lookup_glossary_termOnly readsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
- Tools that change things, listed without credentials: 2 to 3
PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
- Tools that change things, listed without credentials: 1 to 2
Tools4 added, 7 changed.+4 added~7 changedView diff
- Added:list_crawlersOnly reads
- Added:lookup_crawlerOnly reads
- Added:privacy_execute_planChanges things
- Added:privacy_search_apiOnly reads
- Changed:classify_cookieChanges thingsdescription
- Changed:lookup_trackerOnly readsdescription
- Changed:privacy_get_enforcement_caseOnly readsdescription
- Changed:privacy_law25_requirementsOnly readsdescription
- Changed:privacy_list_glossary_termsOnly readsdescription
- Changed:privacy_lookup_glossary_termOnly readsdescription
- Changed:privacy_search_enforcement_actionsOnly readsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http privacy https://movahedi.ca/mcpclaude mcp add --transport http privacy https://movahedi.ca/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__privacy__privacy_search_enforcement_actions",
"mcp__privacy__privacy_get_enforcement_case",
"mcp__privacy__privacy_lookup_glossary_term",
"mcp__privacy__privacy_list_glossary_terms",
"mcp__privacy__privacy_law25_requirements",
"mcp__privacy__lookup_tracker",
"mcp__privacy__lookup_crawler",
"mcp__privacy__list_crawlers",
"mcp__privacy__privacy_search_api",
"mcp__privacy__canadian_privacy_consequential_action_lookup_v1"
],
"ask": [
"mcp__privacy__classify_cookie",
"mcp__privacy__privacy_execute_plan",
"mcp__privacy__canadian_privacy_breach_deadline_calculator_v1"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as privacy. Review it before you use it.
Capability tags behind 1 rule
- mcp__privacy__privacy_list_glossary_terms untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ca.movahedi/privacy/verify?hash=bbc86fe64c65ba02ab14abbd031ef4e5e6a3753c7fb45b217c0a1ec351245fba" | jq -e '.changed == false'Pinned hash bbc86fe64c65, from Nov 10, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ca.movahedi/privacy/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ca.movahedi/privacy)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:46 UTC.
movahedi.ca Privacy Data MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the movahedi.ca Privacy Data MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the movahedi.ca Privacy Data MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the movahedi.ca Privacy Data MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the movahedi.ca Privacy Data MCP server have?
- 13 tools: 3 write, 10 read. classify_cookie, privacy_execute_plan, canadian_privacy_breach_deadline_calculator_v1, privacy_search_enforcement_actions, privacy_get_enforcement_case, privacy_lookup_glossary_term, privacy_list_glossary_terms, privacy_law25_requirements and 5 more.
Does the movahedi.ca Privacy Data MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the movahedi.ca Privacy Data MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the movahedi.ca Privacy Data MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.