io.github.seayniclabs/privacyops
PYPI · PRIVACYOPS-MCP
Track credit-report disputes and draft dispute letters, kept on your computer. Not legal advice.
Available components
Last scanned (6 hours ago)
Scores higher than 80% of PyPI servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to seayniclabs/privacyops). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability56
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 922 tokens (~83/item across 11 items; 9 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → pass ▲ functional
- 28 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/privacyops-mcp@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | seayniclabs/privacyops |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/seayniclabs/privacyops/.github/workflows/release.yml@refs/tags/v0.2.2 |
| Rekor log index | 3525375898 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:6df3dbdfe90a2dba4524f3bef92177619be8e9f449be3d59d466ec18edaa4148 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
disputes_create ~76
Start tracking a dispute. party_type is consumer_reporting_agency or furnisher. Use the item's description, not full account numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| item_description | string | yes | – |
| party_name | string | yes | – |
| party_type | string | yes | – |
| reason | – | – | – |
| sent_date | – | – | – |
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | yes | – |
| due_date | – | – | – |
| due_note | string | yes | – |
| history | array | – | – |
| id | string | yes | – |
| item_description | string | yes | – |
| letter_files | array | – | – |
| party_name | string | yes | – |
| party_type | string | yes | – |
| reason | – | – | – |
| sent_date | – | – | – |
| status | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
disputes_deadlines ~248
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>.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| disclaimer | string | yes | – |
| disputes | array | yes | – |
| has_more | boolean | yes | – |
| next_offset | – | – | – |
| open_total | integer | yes | – |
| overdue_total | integer | yes | – |
| sources | array | yes | – |
No examples provided.
disputes_delete ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| approved_by | – | – | – |
| deleted | boolean | yes | – |
| id | string | yes | – |
| note | – | – | – |
| preview | – | – | – |
No examples provided.
disputes_get ~33
The full record for one dispute: details, due date, letters written, and history.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | yes | – |
| due_date | – | – | – |
| due_note | string | yes | – |
| history | array | – | – |
| id | string | yes | – |
| item_description | string | yes | – |
| letter_files | array | – | – |
| party_name | string | yes | – |
| party_type | string | yes | – |
| reason | – | – | – |
| sent_date | – | – | – |
| status | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
disputes_list ~53
List disputes, newest first. Filter by status or party_type. Page with offset=<next_offset>.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| party_type | – | – | – |
| status | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| disputes | array | yes | – |
| has_more | boolean | yes | – |
| next_offset | – | – | – |
| total | integer | yes | – |
No examples provided.
disputes_update ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| note | – | – | – |
| sent_date | – | – | – |
| status | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | yes | – |
| due_date | – | – | – |
| due_note | string | yes | – |
| history | array | – | – |
| id | string | yes | – |
| item_description | string | yes | – |
| letter_files | array | – | – |
| party_name | string | yes | – |
| party_type | string | yes | – |
| reason | – | – | – |
| sent_date | – | – | – |
| status | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
letters_generate ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_key | – | – | – |
| dispute_id | – | – | – |
| item_description | string | yes | – |
| reason | – | – | – |
| recipient_address | – | – | – |
| recipient_name | – | – | – |
| template | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | string | – | – |
| dispute_id | – | – | – |
| letter_id | string | yes | – |
| path | string | yes | – |
| recipient | – | yes | – |
| template | string | yes | – |
| text | string | yes | – |
No examples provided.
letters_templates ~30
The letter templates, the agencies with checked contact details, and the disclaimer. Read this before generating a letter.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| agencies | array | yes | Only contact details checked on the official site are shown. |
| disclaimer | string | yes | – |
| templates | array | yes | – |
No examples provided.
privacyops_modules ~47
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.
| Name | Type | Req | Description |
|---|---|---|---|
| module | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| config_error | – | – | – |
| config_file | string | yes | – |
| data_dir | string | yes | – |
| disclaimer | string | yes | – |
| homepage | string | – | – |
| modules | array | yes | – |
| publisher | string | – | – |
| skills | array | yes | – |
| version | string | yes | – |
No examples provided.
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.
pypi · privacyops-mcp
claude mcp add seayniclabs-privacyops -- uvx privacyops-mcp
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.