Skills/PyPI/paperless-mcp

paperless-mcp@0.1.0

VERIFIED· not started

Publisher claims: "Model Context Protocol server for Paperless-ngx, backed by pypaperless." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher tb1337 · publishing for 105 daysInstalls 637Last detonated 3 h ago
$claude mcp add paperless-mcp -- uvx paperless-mcp
WatchReport an issue

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

$vet-skills run --net declared -- uvx paperless-mcp

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-14 and scored it 82/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 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsCLAUDE.md:80 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesLocal dev instance credentials live in the git-ignored `.env` (`PAPERLESS_URL`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsCLAUDE.md:91 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesagainst the instance in your `.env`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
MCP server using network transport (SSE/HTTP)AGENTS.md:40 · MCP server using network transport (SSE/HTTP) — data sent over network- top-level: `server.py` (MCPServer wiring, lifespans, stdio + Streamable HTTP transports),Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
Access to sensitive file pathstests/test_config.py:316 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""CLAUDE.md: anything user-facing lands in .env.example in the same change."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/paperless_mcp/__main__.py:104 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesdefault=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsCLAUDE.md:52 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesagainst the live instance from `.env`; the target of the VS Code debug configurationFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_config.py:317 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filestext = (Path(__file__).parent.parent / ".env.example").read_text(encoding="utf-8")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Process kill commandtests/test_lifespan.py:135 · Process kill command — agent can terminate processes"""A Paperless that is down at launch must not kill the MCP session."""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Access to sensitive file pathstests/test_config.py:250 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files""".env ships PAPERLESS_MCP_AUTH_TOKEN= as the documented way to opt out."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsrun/debug.py:29 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesENV_FILE = Path(__file__).resolve().parent.parent / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsAGENTS.md:91 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesagainst the instance in your `.env`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsrun/debug.py:5 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesgit-ignored ``.env`` in the repo root — the same file the server itself reads.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_config.py:290 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""These messages are what an operator sees for a broken .env."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsAGENTS.md:80 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesLocal dev instance credentials live in the git-ignored `.env` (`PAPERLESS_URL`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
MCP server using network transport (SSE/HTTP)CLAUDE.md:40 · MCP server using network transport (SSE/HTTP) — data sent over network- top-level: `server.py` (MCPServer wiring, lifespans, stdio + Streamable HTTP transports),Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
HIGH
Access to sensitive file pathsAGENTS.md:52 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesagainst the live instance from `.env`; the target of the VS Code debug configurationFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsAGENTS.md:81 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files`PAPERLESS_TOKEN`) — copy `.env.example` to `.env`. That file documents every `PAPERLESS_MCP_*`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsCLAUDE.md:81 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files`PAPERLESS_TOKEN`) — copy `.env.example` to `.env`. That file documents every `PAPERLESS_MCP_*`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈9,211 tok
3 files · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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 paperless-mcp@0.1.0 as of 3 h ago. This is the package itself, not its dependencies.