privacyops-mcp@0.2.2
VERIFIED· not startedPublisher claims: "MCP bundle for consumers tracking credit-bureau disputes and drafting dispute letters from fixed templates. Local only." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso cornell.edu, equifax.com, experian.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
out = subprocess.run(["git", "ls-files", "-co", "--exclude-standard"], cwd=root,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.run([sys.executable, "-m", "privacyops_mcp.server", "--doctor"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.r = subprocess.run([sys.executable, str(ROOT / "scripts" / "security_card.py"), "--check"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.bad = subprocess.run([sys.executable, str(tmp_path / "scripts" / "check_skills.py")], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.out.append(("letters", False, f"{letters_dir} is readable by other users. Fix: chmod 700 {letters_dir}"))Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.r = subprocess.run([sys.executable, str(ROOT / "scripts" / "tool_lock.py"), "--check"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.assert "chmod 700" in capsys.readouterr().outFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.out.append(("data folder", False, f"{data_dir} is readable by other users. Fix: chmod 700 {data_dir}"))Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.ok = subprocess.run([sys.executable, str(ROOT / "scripts" / "check_skills.py")], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Writes tool-manifest.lock.json: a SHA-256 of every tool's name, description, input andFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.out.append(("records file", False, f"{records} is readable by other users. Fix: chmod 600 {records}"))Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for privacyops-mcp@0.2.2 as of 35 min ago. This is the package itself, not its dependencies.