Paperless (heimerle) MCP Server

paperless-mcp-server npm v1.2.0

Published by heimerle — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Model Context Protocol server for Paperless-ngx document management system

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 42

Each tool and what it can reach — statically extracted from the published source.

  • download_documentingests untrusted input
  • get_logsreads sensitive data
  • acknowledge_taskno sensitive capability
  • bulk_update_documentsno sensitive capability
  • create_correspondentno sensitive capability
  • create_custom_fieldno sensitive capability
  • create_document_typeno sensitive capability
  • create_saved_viewno sensitive capability
  • create_storage_pathno sensitive capability
  • create_tagno sensitive capability
Show 32 more tools ↓
  • delete_correspondentno sensitive capability
  • delete_custom_fieldno sensitive capability
  • delete_documentno sensitive capability
  • delete_document_typeno sensitive capability
  • delete_saved_viewno sensitive capability
  • delete_storage_pathno sensitive capability
  • delete_tagno sensitive capability
  • get_correspondentno sensitive capability
  • get_custom_fieldno sensitive capability
  • get_documentno sensitive capability
  • get_document_metadatano sensitive capability
  • get_document_suggestionsno sensitive capability
  • get_document_typeno sensitive capability
  • get_saved_viewno sensitive capability
  • get_statisticsno sensitive capability
  • get_storage_pathno sensitive capability
  • get_tagno sensitive capability
  • list_correspondentsno sensitive capability
  • list_custom_fieldsno sensitive capability
  • list_document_typesno sensitive capability
  • list_saved_viewsno sensitive capability
  • list_storage_pathsno sensitive capability
  • list_tagsno sensitive capability
  • list_tasksno sensitive capability
  • search_documentsno sensitive capability
  • update_correspondentno sensitive capability
  • update_custom_fieldno sensitive capability
  • update_documentno sensitive capability
  • update_document_typeno sensitive capability
  • update_saved_viewno sensitive capability
  • update_storage_pathno sensitive capability
  • update_tagno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.2.0 latest A 96/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/paperless-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/paperless-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/paperless-mcp-server"><img src="https://mcptrustchecker.com/registry/paperless-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/paperless-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan paperless-mcp-server --online

Use the free API → How scoring works

Other implementations of Paperless 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

More in API Development