# movahedi.ca Privacy Data (remote · movahedi.ca)

Canadian privacy enforcement, glossary, and Quebec Law 25 guidance for AI agents.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `movahedi.ca`: 77/100 (this document), [markdown](https://verifymcp.io/servers/ca-movahedi-privacy/movahedi.md), [page](https://verifymcp.io/servers/ca-movahedi-privacy/movahedi)

## Channel facts

- Endpoint: `https://movahedi.ca/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 784 tokens (~156/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the movahedi.ca Privacy Data MCP server?

movahedi.ca Privacy Data is a hosted endpoint at https://movahedi.ca/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ca-movahedi-privacy 'https://movahedi.ca/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ca-movahedi-privacy": {
      "url": "https://movahedi.ca/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ca-movahedi-privacy": {
      "type": "http",
      "url": "https://movahedi.ca/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ca-movahedi-privacy]
url = "https://movahedi.ca/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ca-movahedi-privacy": {
      "type": "remote",
      "url": "https://movahedi.ca/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ca-movahedi-privacy --url 'https://movahedi.ca/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ca-movahedi-privacy:
    url: "https://movahedi.ca/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ca-movahedi-privacy": {
      "Transport": "http",
      "Url": "https://movahedi.ca/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ca-movahedi-privacy -t streamable-http -u 'https://movahedi.ca/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ca-movahedi-privacy": {
      "type": "http",
      "url": "https://movahedi.ca/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-03 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-01 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-29 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 72)

First indexed and scored.

## MCP tools (5)

### `privacy_search_enforcement_actions` (~229 tokens)

Search privacy 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.

Input parameters:

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

Output parameters:

- `has_more` (boolean): True when more results exist beyond this page.
- `next_offset` (integer|null): Pass as 'offset' in the next call to continue paging. Null when has_more is false.
- `results` (array): Matching enforcement actions.
- `total_count` (integer): Total number of matches across all pages.
- `truncated` (boolean): True when results were shortened to fit the 50 KB output cap. Use the paginated REST API for the full set.

### `privacy_get_enforcement_case` (~98 tokens)

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.

Input parameters:

- `id` (string, required): The case ID from a search result.

Output parameters:

- `case` (object)

### `privacy_lookup_glossary_term` (~112 tokens)

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.

Input parameters:

- `term` (string, required): The glossary slug.

Output parameters:

- `term` (object)

### `privacy_list_glossary_terms` (~133 tokens)

Browse the privacy glossary

Browse the 260+ 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.

Input parameters:

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

Output parameters:

- `has_more` (boolean): True when more results exist beyond this page.
- `next_offset` (integer|null): Pass as 'offset' in the next call to continue paging. Null when has_more is false.
- `terms` (array): Matching glossary terms.
- `total_count` (integer): Total number of matches across all pages.
- `truncated` (boolean): True when results were shortened to fit the 50 KB output cap. Use the paginated REST API for the full set.

### `privacy_law25_requirements` (~121 tokens)

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

Input parameters:

- `category` (string): Only requirements in this category. Omit for the full checklist.

Output parameters:

- `categories` (array): All available categories for the 'category' filter.
- `requirements` (array): Law 25 requirements.
- `total_count` (integer): Number of requirements returned.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ca-movahedi-privacy/movahedi#diagnostics

## Score history

- 2026-10-04: 77
- 2026-10-03: 77
- 2026-10-02: 76
- 2026-10-01: 76
- 2026-09-30: 75
- 2026-09-29: 75
- 2026-09-28: 74
- 2026-09-27: 74
- 2026-09-26: 73
- 2026-09-25: 73
- 2026-09-24: 72

## Common questions

### What is the movahedi.ca Privacy Data MCP server?

movahedi.ca Privacy Data is an MCP server listed in the public MCP registry as ca.movahedi/privacy. Canadian privacy enforcement, glossary, and Quebec Law 25 guidance for AI agents. This page covers its hosted endpoint (https://movahedi.ca/mcp).

### Is the movahedi.ca Privacy Data MCP server safe to use?

movahedi.ca Privacy Data scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the movahedi.ca Privacy Data MCP server expose?

movahedi.ca Privacy Data exposes 5 tools: privacy_search_enforcement_actions, privacy_get_enforcement_case, privacy_lookup_glossary_term, privacy_list_glossary_terms, privacy_law25_requirements. Their descriptions and schemas cost roughly 693 tokens of context every time the server is loaded.

### Does the movahedi.ca Privacy Data MCP server require authentication?

No. We connected to movahedi.ca Privacy Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the movahedi.ca Privacy Data MCP server still maintained?

movahedi.ca Privacy Data is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://movahedi.ca/mcp
- Repository: https://github.com/movahedi-ca/movahedi-ca
- Website: https://movahedi.ca/developers/
- Changelog RSS feed: https://verifymcp.io/servers/ca-movahedi-privacy/movahedi.xml
- Changelog JSON feed: https://verifymcp.io/servers/ca-movahedi-privacy/movahedi.json
- HTML version of this page: https://verifymcp.io/servers/ca-movahedi-privacy/movahedi