movahedi.ca Privacy Data
Canadian privacy enforcement, glossary, and Quebec Law 25 guidance for AI agents.
| Endpoint | https://movahedi.ca/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 11 tools · grade B (82) · pin ts_af3d7c020dd0e48b2e1a18439606993e · protocol 2025-06-18 |
| First / last listed | 2026-11-01 00:56 UTC / 2026-11-01 00:56 UTC |
| Grade over time | 2026-11-01: B (82), 11 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: privacy_search_enforcement_actions privacy_get_enforcement_case privacy_lookup_glossary_term privacy_list_glossary_terms privacy_law25_requirements classify_cookie lookup_tracker lookup_crawler list_crawlers privacy_search_api privacy_execute_plan
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, params: query, regulator, year, limit, offset |
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 params: id* |
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 s params: term* |
privacy_list_glossary_terms | Browse the 324-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 params: query, starts_with, limit, offset |
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 fil params: category |
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-pa params: name* |
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 params: query, vendor, limit, offset |
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 params: token* |
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 wan params: query, operator, purpose, status, limit, offset |
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 ca params: query, limit |
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 fai params: operations |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.