# io.github.seayniclabs/privacyops (pypi · privacyops-mcp)

Track credit-report disputes and draft dispute letters, kept on your computer. Not legal advice.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `privacyops-mcp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/seayniclabs-privacyops/privacyops-mcp.md), [page](https://verifymcp.io/servers/seayniclabs-privacyops/privacyops-mcp)

## Channel facts

- Registry: `pypi`
- Package: `privacyops-mcp`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to seayniclabs/privacyops).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 56/100
  - 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 922 tokens (~83/item across 11 items; 9 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 11 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 io.github.seayniclabs/privacyops MCP server?

io.github.seayniclabs/privacyops runs locally as a PyPI package, launched with uvx privacyops-mcp. 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 seayniclabs-privacyops -- uvx privacyops-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "seayniclabs-privacyops": {
      "command": "uvx",
      "args": [
        "privacyops-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "seayniclabs-privacyops": {
      "command": "uvx",
      "args": [
        "privacyops-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add seayniclabs-privacyops -- uvx privacyops-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "seayniclabs-privacyops": {
      "type": "local",
      "command": [
        "uvx",
        "privacyops-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add seayniclabs-privacyops --command uvx --arg privacyops-mcp
```

### Hermes

```yaml
mcp_servers:
  seayniclabs-privacyops:
    command: "uvx"
    args: ["privacyops-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "seayniclabs-privacyops": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "privacyops-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add seayniclabs-privacyops -t stdio -c uvx -a privacyops-mcp
```

### Other

```json
{
  "mcpServers": {
    "seayniclabs-privacyops": {
      "command": "uvx",
      "args": [
        "privacyops-mcp"
      ]
    }
  }
}
```

## 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-11-05 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-04 (score 65, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-03 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 64, +1)

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

### 2026-10-31 (score 63, +1)

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

### 2026-10-30 (score 62, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-29 (score 77, +16)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Security disclosure: fail → pass

### 2026-10-28 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (9)

### `disputes_list` (~53 tokens)

List disputes, newest first. Filter by status or party_type. Page with offset=<next_offset>.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `party_type`
- `status`

Output parameters:

- `disputes` (array)
- `has_more` (boolean)
- `next_offset`
- `total` (integer)

### `disputes_get` (~33 tokens)

The full record for one dispute: details, due date, letters written, and history.

Input parameters:

- `id` (string, required)

Output parameters:

- `created_at` (string)
- `due_date`
- `due_note` (string)
- `history` (array)
- `id` (string)
- `item_description` (string)
- `letter_files` (array)
- `party_name` (string)
- `party_type` (string)
- `reason`
- `sent_date`
- `status` (string)
- `updated_at` (string)

### `disputes_deadlines` (~248 tokens)

Open disputes (draft, sent, response_received) with the statutory response deadline for each.
An agency must reinvestigate within 30 days of receiving the dispute, 15 U.S.C. 1681i(a)(1)(A)
(https://www.law.cornell.edu/uscode/text/15/1681i). A furnisher must report results before that
period ends, 15 U.S.C. 1681s-2(a)(8)(E)(iii) and (b)(2) (https://www.law.cornell.edu/uscode/text/15/1681s-2).
Counted from the sent date you recorded, so the real date is the same or later. Returns days remaining,
an overdue flag (past the 30-day date), the next action, and the facts the tool cannot know (the start
of the clock, the 15-day extension, a furnisher's extension). Not legal advice. Set as_of (YYYY-MM-DD) to
check another day. Page with offset=<next_offset>.

Input parameters:

- `as_of`
- `limit` (integer)
- `offset` (integer)

Output parameters:

- `as_of` (string)
- `disclaimer` (string)
- `disputes` (array)
- `has_more` (boolean)
- `next_offset`
- `open_total` (integer)
- `overdue_total` (integer)
- `sources` (array)

### `disputes_create` (~76 tokens)

Start tracking a dispute. party_type is consumer_reporting_agency or furnisher.
Use the item's description, not full account numbers.

Input parameters:

- `item_description` (string, required)
- `party_name` (string, required)
- `party_type` (string, required)
- `reason`
- `sent_date`
- `status` (string)

Output parameters:

- `created_at` (string)
- `due_date`
- `due_note` (string)
- `history` (array)
- `id` (string)
- `item_description` (string)
- `letter_files` (array)
- `party_name` (string)
- `party_type` (string)
- `reason`
- `sent_date`
- `status` (string)
- `updated_at` (string)

### `disputes_update` (~66 tokens)

Change a dispute's status, set its sent date, or add a note. Every change is recorded in history.
Setting status to sent without a sent date uses today's date.

Input parameters:

- `id` (string, required)
- `note`
- `sent_date`
- `status`

Output parameters:

- `created_at` (string)
- `due_date`
- `due_note` (string)
- `history` (array)
- `id` (string)
- `item_description` (string)
- `letter_files` (array)
- `party_name` (string)
- `party_type` (string)
- `reason`
- `sent_date`
- `status` (string)
- `updated_at` (string)

### `disputes_delete` (~73 tokens)

Delete a dispute record. Without confirm=true this only returns a preview. With confirm=true
the person is asked to approve (unless deletes are pre-approved in settings). Letter files on
disk are not deleted. The assistant cannot approve on the person's behalf.

Input parameters:

- `confirm` (boolean)
- `id` (string, required)

Output parameters:

- `approved_by`
- `deleted` (boolean)
- `id` (string)
- `note`
- `preview`

### `letters_templates` (~30 tokens)

The letter templates, the agencies with checked contact details, and the disclaimer. Read this before generating a letter.

Output parameters:

- `agencies` (array): Only contact details checked on the official site are shown.
- `disclaimer` (string)
- `templates` (array)

### `letters_generate` (~119 tokens)

Write a dispute letter from a fixed template to a text file. Your name, address and signature are
placeholders to fill in by hand. For a credit agency pass agency_key (equifax, experian, transunion) or
recipient_name. Pass dispute_id to attach the letter to a dispute record. Not legal advice.

Input parameters:

- `agency_key`
- `dispute_id`
- `item_description` (string, required)
- `reason`
- `recipient_address`
- `recipient_name`
- `template` (string, required)

Output parameters:

- `disclaimer` (string)
- `dispute_id`
- `letter_id` (string)
- `path` (string)
- `recipient`
- `template` (string)
- `text` (string)

### `privacyops_modules` (~47 tokens)

Which modules are on, what each tool does, where your data is kept, the skills, and the disclaimer.
Pass a module name for its full settings list.

Input parameters:

- `module`

Output parameters:

- `config_error`
- `config_file` (string)
- `data_dir` (string)
- `disclaimer` (string)
- `homepage` (string)
- `modules` (array)
- `publisher` (string)
- `skills` (array)
- `version` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/seayniclabs-privacyops/privacyops-mcp#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 65
- 2026-11-03: 79
- 2026-11-02: 64
- 2026-11-01: 63
- 2026-10-31: 63
- 2026-10-30: 62
- 2026-10-29: 77
- 2026-10-28: 61
- 2026-10-27: 60

## Common questions

### What is the io.github.seayniclabs/privacyops MCP server?

io.github.seayniclabs/privacyops is an MCP server listed in the public MCP registry as io.github.seayniclabs/privacyops. Track credit-report disputes and draft dispute letters, kept on your computer. Not legal advice. This page covers its PyPI package (privacyops-mcp).

### Is the io.github.seayniclabs/privacyops MCP server safe to use?

io.github.seayniclabs/privacyops scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 io.github.seayniclabs/privacyops MCP server expose?

io.github.seayniclabs/privacyops exposes 9 tools: disputes_list, disputes_get, disputes_deadlines, disputes_create, disputes_update, and 4 more. Their descriptions and schemas cost roughly 745 tokens of context every time the server is loaded.

### Is the io.github.seayniclabs/privacyops MCP server still maintained?

io.github.seayniclabs/privacyops is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.seayniclabs/privacyops MCP server under?

io.github.seayniclabs/privacyops declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/privacyops-mcp/
- Socket report: https://socket.dev/pypi/package/privacyops-mcp
- Repository: https://github.com/seayniclabs/privacyops
- Changelog RSS feed: https://verifymcp.io/servers/seayniclabs-privacyops/privacyops-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/seayniclabs-privacyops/privacyops-mcp.json
- HTML version of this page: https://verifymcp.io/servers/seayniclabs-privacyops/privacyops-mcp