Paperless-NGX (cubinet-code) MCP Server

paperless-ngx-mcp npm v3.1.1 Source verified

Published by cubinet-code — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Lets AI assistants manage Paperless-NGX documents, tags, correspondents, document types, custom fields, saved views, storage paths, workflows, share links, notes, trash, and tasks via the Paperless-NGX API.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/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 = 97/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 − 3 = 97. 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

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 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([list_custom_fields, list_document_types, download_document, download_documents_bulk, list_tags]) co-exist with external-action tools ([create_workflow_action]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [list_custom_fields, list_document_types, download_document, download_documents_bulk, list_tags] → sinks [create_workflow_action]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow list_custom_fields → create_workflow_action

Tools 75

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

  • create_workflow_actionnetwork egress
  • download_documentingests untrusted input
  • download_documents_bulkingests untrusted input
  • list_custom_fieldsingests untrusted input
  • list_document_typesingests untrusted input
  • list_tagsingests untrusted input
  • acknowledge_tasksno sensitive capability
  • create_correspondentno sensitive capability
  • create_custom_fieldno sensitive capability
  • create_document_noteno sensitive capability
Show 65 more tools ↓
  • create_document_typeno sensitive capability
  • create_saved_viewno sensitive capability
  • create_share_linkno sensitive capability
  • create_storage_pathno sensitive capability
  • create_tagno sensitive capability
  • create_workflow_triggerno sensitive capability
  • delete_correspondentno sensitive capability
  • delete_custom_fieldno sensitive capability
  • delete_documentno sensitive capability
  • delete_document_noteno sensitive capability
  • delete_document_typeno sensitive capability
  • delete_saved_viewno sensitive capability
  • delete_share_linkno sensitive capability
  • delete_storage_pathno sensitive capability
  • delete_tagno sensitive capability
  • delete_workflow_actionno sensitive capability
  • delete_workflow_triggerno sensitive capability
  • edit_custom_fields_bulkno sensitive capability
  • edit_documents_bulkno sensitive capability
  • email_documentno sensitive capability
  • empty_trashno sensitive capability
  • get_correspondentno sensitive capability
  • get_custom_fieldno sensitive capability
  • get_documentno sensitive capability
  • get_document_contentno sensitive capability
  • get_document_historyno sensitive capability
  • get_document_metadatano sensitive capability
  • get_document_previewno sensitive capability
  • get_document_suggestionsno sensitive capability
  • get_document_thumbnailno sensitive capability
  • get_document_typeno sensitive capability
  • get_next_asnno sensitive capability
  • get_saved_viewno sensitive capability
  • get_share_linkno sensitive capability
  • get_statisticsno sensitive capability
  • get_storage_pathno sensitive capability
  • get_tagno sensitive capability
  • get_workflow_actionno sensitive capability
  • get_workflow_triggerno sensitive capability
  • list_correspondentsno sensitive capability
  • list_document_notesno sensitive capability
  • list_document_share_linksno sensitive capability
  • list_documentsno sensitive capability
  • list_saved_viewsno sensitive capability
  • list_share_linksno sensitive capability
  • list_storage_pathsno sensitive capability
  • list_tasksno sensitive capability
  • list_trashno sensitive capability
  • list_workflow_actionsno sensitive capability
  • list_workflow_triggersno sensitive capability
  • post_documentno sensitive capability
  • restore_from_trashno sensitive capability
  • search_autocompleteno sensitive capability
  • search_documentsno sensitive capability
  • test_storage_pathno 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_share_linkno sensitive capability
  • update_storage_pathno sensitive capability
  • update_tagno sensitive capability
  • update_workflow_actionno sensitive capability
  • update_workflow_triggerno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 3

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
v3.1.1 latest A 97/100 1 1.13.0 2026-08-25
v3.0.0 A 97/100 1 1.12.1 2026-08-04
v0.1.6 A 97/100 1 1.12.1 2026-07-27

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 · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/paperless-ngx-mcp/badge.svg)](https://mcptrustchecker.com/registry/paperless-ngx-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/paperless-ngx-mcp"><img src="https://mcptrustchecker.com/registry/paperless-ngx-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/paperless-ngx-mcp/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-ngx-mcp --online

Use the free API → How scoring works

Other implementations of Paperless-NGX 1

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

More in Files & Storage