Official MCP RegistryListed
movahedi.ca Privacy Data
Canadian privacy enforcement, glossary, and Quebec Law 25 guidance for AI agents.
First seen 2 Oct 2026. Evidence as of 28 Oct 2026.
11
Tools
From an anonymous probe
1
Source listings
Each with its own history
26
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| classify_cookie | 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. | Read-only |
| list_crawlers | 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. | Read-only |
| lookup_crawler | 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. | Read-only |
| lookup_tracker | 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. | Read-only |
| privacy_execute_plan | 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. | Read-only |
| privacy_get_enforcement_case | 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. | Read-only |
| privacy_law25_requirements | 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. | Read-only |
| privacy_list_glossary_terms | Browse the 320-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. 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. | Read-only |
| privacy_lookup_glossary_term | 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. 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. | Read-only |
| privacy_search_api | 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. | Read-only |
| privacy_search_enforcement_actions | 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. | Read-only |
Change history
- privacy_list_glossary_terms: description changed (+"320-term" -"319-term")
- server instructions changed (+"320" -"319")
- privacy_search_enforcement_actions: description changed (+"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.")
- privacy_search_api: tool added
- privacy_lookup_glossary_term: description changed (+"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.")
- privacy_list_glossary_terms: description changed (+"319-term" +"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." -"318-term")
- privacy_law25_requirements: description changed (+"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.")
- privacy_get_enforcement_case: description changed (+"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.")
- privacy_execute_plan: tool added
- lookup_tracker: description changed (+"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.")
- lookup_crawler: description changed (+"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.")
- list_crawlers: description changed (+"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.")
- classify_cookie: description changed (+"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.")
- server instructions changed (+"319" +"For work that needs several lookups, prefer one privacy_execute_plan call over many single-tool calls. When unsure which operation fits, use privacy_search_api first." -"318")
- privacy_list_glossary_terms: description changed (+"318-term" -"317-term")
- server instructions changed (+"318" -"317")
- privacy_list_glossary_terms: description changed (+"317-term" -"315-term")
- lookup_crawler: tool added
- list_crawlers: tool added
- server instructions changed (+"317" +"It also carries a registry of 51 AI crawlers: what each user-agent token is for (training, search indexing, or user-triggered fetching) and whether it honors robots.txt." +"data, or what an AI crawler is and what it does.")
- privacy_list_glossary_terms: description changed (+"315-term" -"313-term")
- server instructions changed (+"315" -"313")
- privacy_list_glossary_terms: description changed (+"313-term" -"260+ term")
- lookup_tracker: tool added
- classify_cookie: tool added
- server instructions changed (+"313" +"checklist, and a knowledge base of 202 cookie and tracker patterns that classifies cookies by the organisation that receives the data, not only by the domain that set them." +"requirements, or what a cookie or tracker is and who receives its data.")
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | ca.movahedi/privacy | 2 Oct 2026 | 28 Oct 2026 | 1 |