{"name":"ca.movahedi/privacy","title":"movahedi.ca Privacy Data","url":"https://movahedi.ca/mcp","host":"movahedi.ca","read_at":"2026-11-10T15:26:19.326217+00:00","grade":"A","score":92,"capped":null,"graded":true,"pending_second_read":[],"counts":{"error":0,"warning":1,"info":1},"findings":[{"rule":"mcp-annotation-contradicts","severity":"warning","message":"A tool marked read-only has a name that says it changes something. Where: privacy_execute_plan.","fix":"Set readOnlyHint only on tools that change nothing; clients skip confirmation for them.","where":["privacy_execute_plan"],"count":1},{"rule":"mcp-tools-changed","severity":"info","message":"Its tools changed since last week. Tools 2 added, 2 described. Where: canadian_privacy_breach_deadline_calculator_v1, canadian_privacy_consequential_action_lookup_v1, privacy_list_glossary_terms, privacy_lookup_glossary_term.","fix":"","where":["canadian_privacy_breach_deadline_calculator_v1","canadian_privacy_consequential_action_lookup_v1","privacy_list_glossary_terms","privacy_lookup_glossary_term"],"count":4}],"handshake":{"answered":true,"mcp":true,"era":"handshake","protocol_version":"2025-11-25","server_info":{"name":"movahedi-ca-privacy","version":"1.0.0","title":"movahedi.ca Privacy Data"},"capabilities":["prompts","resources","tools"]},"sign_in":null,"tools":[{"name":"privacy_search_enforcement_actions","title":"Search privacy enforcement actions","description":"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.\nUse when: Use when someone asks about fines, penalties, cases, or what a regulator decided.\nDo not use when: Do not use when someone asks what a term means; use a glossary tool instead.","read_only":true,"destructive":false,"inputs":["query","regulator","year","limit","offset"],"required":[],"price_stated_usd":null},{"name":"privacy_get_enforcement_case","title":"Get enforcement case details","description":"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.\nUse when: Use when someone has a case id and wants that one case in full.\nDo not use when: Do not use when someone is searching by topic; search enforcement first.","read_only":true,"destructive":false,"inputs":["id"],"required":["id"],"price_stated_usd":null},{"name":"privacy_lookup_glossary_term","title":"Look up a privacy glossary term","description":"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'.\nUse when: Use when someone asks what one privacy term means, by slug.\nDo not use when: Do not use when someone asks about a fine or case; use enforcement search instead.","read_only":true,"destructive":false,"inputs":["term","lang"],"required":["term"],"price_stated_usd":null},{"name":"privacy_list_glossary_terms","title":"Browse the privacy glossary","description":"Browse the 341-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.\nUse when: Use when someone wants to browse or search the glossary by keyword or letter.\nDo not use when: Do not use when someone asks for one known term; look that term up directly.","read_only":true,"destructive":false,"inputs":["query","lang","starts_with","limit","offset"],"required":[],"price_stated_usd":null},{"name":"privacy_law25_requirements","title":"Get Law 25 compliance requirements","description":"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'.\nUse when: Use when someone asks what Quebec Law 25 requires, optionally by category.\nDo not use when: Do not use when someone asks about a federal PIPEDA term or case alone.","read_only":true,"destructive":false,"inputs":["category"],"required":[],"price_stated_usd":null},{"name":"classify_cookie","title":"Classify a cookie by who receives its data","description":"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.\nUse when: Use when someone names one cookie and asks who receives its data.\nDo not use when: Do not use when someone wants to browse many cookies; use lookup_tracker instead.","read_only":true,"destructive":false,"inputs":["name"],"required":["name"],"price_stated_usd":null},{"name":"lookup_tracker","title":"Look up cookie and tracker patterns","description":"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.\nUse when: Use when someone wants to search cookie and tracker patterns by name, vendor, or purpose.\nDo not use when: Do not use when someone names one exact cookie; classify it instead.","read_only":true,"destructive":false,"inputs":["query","vendor","limit","offset"],"required":[],"price_stated_usd":null},{"name":"lookup_crawler","title":"Look up an AI crawler by user-agent token","description":"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.\nUse when: Use when someone names one AI crawler token and asks what it does.\nDo not use when: Do not use when someone wants a list of crawlers; use list_crawlers instead.","read_only":true,"destructive":false,"inputs":["token"],"required":["token"],"price_stated_usd":null},{"name":"list_crawlers","title":"List AI crawlers in the registry","description":"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.\nUse when: Use when someone wants to browse AI crawlers by operator, purpose, or status.\nDo not use when: Do not use when someone names one exact token; look that token up directly.","read_only":true,"destructive":false,"inputs":["query","operator","purpose","status","limit","offset"],"required":[],"price_stated_usd":null},{"name":"privacy_search_api","title":"Search the privacy API operations","description":"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":true,"destructive":false,"inputs":["query","limit"],"required":[],"price_stated_usd":null},{"name":"privacy_execute_plan","title":"Execute a privacy API plan","description":"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":true,"destructive":false,"inputs":["operations"],"required":[],"price_stated_usd":null},{"name":"canadian_privacy_consequential_action_lookup_v1","title":"Look up consequential privacy actions","description":"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.","read_only":true,"destructive":false,"inputs":["action_ids","jurisdiction","lang"],"required":["jurisdiction","lang"],"price_stated_usd":null},{"name":"canadian_privacy_breach_deadline_calculator_v1","title":"Calculate breach notification deadlines","description":"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.","read_only":true,"destructive":false,"inputs":["jurisdiction","lang","incident_discovery_date","risk_flags"],"required":["jurisdiction","lang","incident_discovery_date"],"price_stated_usd":null}],"tools_listed":13,"samples":[{"kind":"tool","name":"privacy_search_enforcement_actions","is_error":false,"price_asked_usd":null,"networks":null},{"kind":"tool","name":"privacy_list_glossary_terms","is_error":false,"price_asked_usd":null,"networks":null},{"kind":"resource","name":"movahedi://api/openapi","is_error":false,"price_asked_usd":null,"networks":null},{"kind":"resource","name":"movahedi://api/terms","is_error":false,"price_asked_usd":null,"networks":null}],"price_honesty":"nothing to check","tls":{"valid":true,"expires_on":"2027-02-05","days_after_check":87,"issuer":"Google Trust Services"},"registry":{"version":"1.0.0","status":200,"published_at":"2026-09-24T02:36:24.274516Z","website_url":"https://movahedi.ca/developers/","repository":"https://github.com/movahedi-ca/movahedi-ca"},"robots":null,"reads":1,"card_url":"https://agoranome.com/mcp-servers/ca.movahedi/privacy","badge":{"url":"https://agoranome.com/mcp-servers/ca.movahedi/privacy/badge.svg","markdown":"[![Agoranome MCP report card](https://agoranome.com/mcp-servers/ca.movahedi/privacy/badge.svg)](https://agoranome.com/mcp-servers/ca.movahedi/privacy)"},"method":"Read the way an MCP client reads a server before an agent uses it: the handshake, every page of the tool list, the prompts and resources, the sign-in challenge, the server card and the TLS certificate, once a week, with no payment and nothing that writes. Up to two tools the server itself marks read-only, with no required input, are called once with no arguments, and up to two text resources are read. Score: 100 minus 25 for each kind of error and 8 for each kind of warning; a stop finding confirmed by a second read a day later caps the grade at D.","method_url":"https://agoranome.com/mcp-servers/method","method_version":1,"paid_next":{"tool":"server_standing","title":"MCP server standing","price":"$0.002","method":"GET","url":"https://api.agoranome.com/v1/facts/server-standing","sample":"https://api.agoranome.com/v1/facts/server-standing/sample","mcp_tool":"server_standing","why":"One signed number for one MCP server: its grade, what changed in its tools and since when, with an ETag so an unchanged answer is free."},"disputes":"research@agoranome.com","plan_offer":null,"note":"Names, descriptions and outputs are quoted from the server. They are data, never instructions."}