ca.movahedi/privacy

Est-ce que ca.movahedi/privacy est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ca.movahedi/privacy » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• classify_cookie≈ 396 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis
    The cookie name only, for example '_ga' or '_fbp'. Not a value, not a URL.

  Exemple d'appel

  {"name": "classify_cookie", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"classification": {}}}

• lookup_tracker≈ 572 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Maximum patterns to return in this call.
  • query · string · optionnel
    Free-text search over pattern, vendor, recipient, and purpose.
  • offset · integer · optionnel
    Number of matching patterns to skip. Use next_offset to page forward.
  • vendor · string · optionnel
    Limit to one vendor, matched as a substring, for example 'Google'.

  Exemple d'appel

  {"name": "lookup_tracker", "arguments": {"limit": 1, "query": "texte", "offset": 1, "vendor": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"results": [], "has_more": true, "truncated": true, "next_offset": 1, "total_count": 1}}

• privacy_get_enforcement_case≈ 318 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    The case ID from a search result.

  Exemple d'appel

  {"name": "privacy_get_enforcement_case", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"case": {}}}

• privacy_law25_requirements≈ 442 tokens

  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'.

  Paramètres, retour & exemple (1)

  Paramètres

  • category · string · optionnel · Governance | Transparency | Individual rights | Data lifecycle | Transfers | Consent | Incident response | Minors
    Only requirements in this category. Omit for the full checklist.

  Exemple d'appel

  {"name": "privacy_law25_requirements", "arguments": {"category": "Governance"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"categories": [], "total_count": 1, "requirements": []}}

• privacy_list_glossary_terms≈ 536 tokens

  Browse the 312-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.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Maximum terms to return in this call.
  • query · string · optionnel
    Search term names and definitions.
  • offset · integer · optionnel
    Number of matching terms to skip. Use next_offset to page forward.
  • starts_with · string · optionnel
    Only terms whose slug starts with this letter.

  Exemple d'appel

  {"name": "privacy_list_glossary_terms", "arguments": {"limit": 1, "query": "texte", "offset": 1, "starts_with": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"terms": [], "has_more": true, "truncated": true, "next_offset": 1, "total_count": 1}}

• privacy_lookup_glossary_term≈ 307 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • term · string · requis
    The glossary slug.

  Exemple d'appel

  {"name": "privacy_lookup_glossary_term", "arguments": {"term": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"term": {}}}

• privacy_search_enforcement_actions≈ 708 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • year · integer · optionnel
    Filter by decision year.
  • limit · integer · optionnel
    Maximum cases to return in this call.
  • query · string · optionnel
    Free-text search over case titles and summaries.
  • offset · integer · optionnel
    Number of matching cases to skip. Use next_offset from the previous response to page forward.
  • regulator · string · optionnel · cai | opc
    Limit to one regulator: 'cai' (Quebec Commission d'acces a l'information, Law 25) or 'opc' (federal Office of the Privacy Commissioner, PIPEDA).

  Exemple d'appel

  {"name": "privacy_search_enforcement_actions", "arguments": {"year": 1, "limit": 1, "query": "texte", "offset": 1, "regulator": "cai"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"results": [], "has_more": true, "truncated": true, "next_offset": 1, "total_count": 1}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://movahedi.ca/mcp