Lets an assistant search Canadian privacy enforcement actions, look up privacy terms, check Quebec Law 25 requirements, and classify cookies and trackers.
What you can do
Provides seven tools over a remote endpoint. It searches verified Canadian privacy enforcement actions (CAI orders under Quebec Law 25 and OPC findings under PIPEDA) and retrieves a full case record with summary, outcome, penalty amount and official source link. It also offers a 315-term Canadian privacy glossary with lookup and paginated browsing, a Quebec Law 25 compliance checklist, and cookie and tracker tools that classify a cookie by name or search a knowledge base by vendor, recipient organisation or purpose.
When to use it
Useful when answering questions about Canadian privacy fines, regulator decisions or investigations, when a precise definition of a privacy term is needed, or when checking Law 25 obligations. Also suited to cookie and tracker questions such as whether a cookie is first- or third-party and who receives its data.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. No authentication is declared. Network access to the provider's endpoint is needed.
Before you install
The server is read-only reference lookup; no writes, payments or credentials are described. Case details, definitions and cookie classifications come from a third party, so verify important compliance conclusions against the official regulator sources the tools link to.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ca.movahedi%2Fprivacy/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametersyearlimitqueryoffsetregulator
privacy_get_enforcement_case
Get enforcement case details
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.
Parametersidrequired
privacy_lookup_glossary_term
Look up a privacy 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.
Parameterstermrequired
privacy_list_glossary_terms
Browse the privacy glossary
Browse the 315-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.
Parameterslimitqueryoffsetstarts_with
privacy_law25_requirements
Get Law 25 compliance 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'.
Parameterscategory
classify_cookie
Classify a cookie by who receives its data
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.
Parametersnamerequired
lookup_tracker
Look up cookie and tracker patterns
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.
Parameterslimitqueryoffsetvendor
Version history
1
v1.0.0LatestSep 24, 2026
Score
75%
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.
