PrivacyOps
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIVACYOPS_CONFIG | No | Optional path to the config file. Default is ~/.config/privacyops/config.toml. | |
| PRIVACYOPS_DATA_DIR | No | Folder for your records and letters. Default is ~/.local/share/privacyops. | |
| PRIVACYOPS_APPROVAL_LOG | No | Path of the approval log. Default is ~/.local/state/privacyops/approvals.jsonl. | |
| PRIVACYOPS_LETTERS_ENABLED | No | Set to false to turn the letters module off. | |
| PRIVACYOPS_DISPUTES_ENABLED | No | Set to false to turn the disputes module off. | |
| PRIVACYOPS_DISPUTES_ALLOW_DELETE | No | false by default: you approve each delete. true lets the assistant delete a dispute record without asking. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| disputes_listA | List disputes, newest first. Filter by status or party_type. Page with offset=<next_offset>. |
| disputes_getB | The full record for one dispute: details, due date, letters written, and history. |
| disputes_deadlinesA | 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>. |
| disputes_createC | Start tracking a dispute. party_type is consumer_reporting_agency or furnisher. Use the item's description, not full account numbers. |
| disputes_updateA | 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. |
| disputes_deleteA | 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. |
| letters_templatesA | The letter templates, the agencies with checked contact details, and the disclaimer. Read this before generating a letter. |
| letters_generateB | 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. |
| privacyops_modulesB | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| dispute-walkthrough | Walk a person through one credit-report dispute with PrivacyOps, from gathering facts to following up. Covers what to gather, which letter template to use, how to send it by certified mail, when to follow up, and how to log each step with the tools. Use when the user wants to dispute an item on a credit report, asks how to write or send a dispute letter, or asks what to do after an agency or a company answers. |
| getting-started | Set up and check the PrivacyOps MCP bundle, which tracks credit-report disputes and drafts dispute letters on this computer. Use when the user installs PrivacyOps, asks what it does, gets an error that starts with "privacyops.", wants to find where their records are, or wants to switch a module on or off. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| dispute-walkthrough/SKILL.md | |
| getting-started/SKILL.md |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: CRUD for disputes, deadline tracking, letter template discovery/generation, and module metadata. The disputes tools are differentiated by action and output focus, and letters_templates vs letters_generate are easy to distinguish.
Most tools follow a consistent resource_action pattern such as disputes_list, disputes_get, disputes_create, and letters_generate. The main deviations are letters_templates (noun rather than verb) and privacyops_modules (meta-tool), but the naming remains predictable and readable.
Nine tools is well-scoped for a dispute-tracking and letter-generation server. Each tool earns its place, with no excessive surface or trivial filler.
The surface covers dispute CRUD, deadline tracking, letter template discovery, letter generation, and module information. Minor gaps exist around managing generated letters or templates, but core workflows are complete.