Docmost (johnkattenhorn) MCP Server

@johnkattenhorn/docmost-mcp npm v1.0.0

Published by @johnkattenhorn — 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.

MCP server for Docmost - connects AI assistants to standard Docmost instances

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 1

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

Untrusted-input tools ([docmost_get_page, docmost_get_page_history]) co-exist with external-action tools ([docmost_create_comment]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [docmost_get_page, docmost_get_page_history] → sinks [docmost_create_comment]

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

Location: flow docmost_get_page → docmost_create_comment

Tools 34

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

  • docmost_create_commentnetwork egress
  • docmost_get_pageingests untrusted input
  • docmost_get_page_historyingests untrusted input
  • docmost_bulk_create_pagesno sensitive capability
  • docmost_create_pageno sensitive capability
  • docmost_create_spaceno sensitive capability
  • docmost_delete_commentno sensitive capability
  • docmost_delete_pageno sensitive capability
  • docmost_delete_spaceno sensitive capability
  • docmost_embed_from_cdnno sensitive capability
Show 24 more tools ↓
  • docmost_embed_imageno sensitive capability
  • docmost_export_pageno sensitive capability
  • docmost_get_attachment_infono sensitive capability
  • docmost_get_current_userno sensitive capability
  • docmost_get_recent_pagesno sensitive capability
  • docmost_get_spaceno sensitive capability
  • docmost_get_workspaceno sensitive capability
  • docmost_import_pageno sensitive capability
  • docmost_insert_drawio_blockno sensitive capability
  • docmost_insert_drawio_from_cdnno sensitive capability
  • docmost_insert_excalidraw_blockno sensitive capability
  • docmost_insert_excalidraw_from_cdnno sensitive capability
  • docmost_list_commentsno sensitive capability
  • docmost_list_pagesno sensitive capability
  • docmost_list_spacesno sensitive capability
  • docmost_list_workspace_membersno sensitive capability
  • docmost_move_pageno sensitive capability
  • docmost_move_page_to_parentno sensitive capability
  • docmost_searchno sensitive capability
  • docmost_search_suggestno sensitive capability
  • docmost_update_pageno sensitive capability
  • docmost_update_page_markdownno sensitive capability
  • docmost_update_spaceno sensitive capability
  • docmost_upload_attachmentno 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 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.0.0 latest A 96/100 1 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/johnkattenhorn-docmost-mcp/badge.svg)](https://mcptrustchecker.com/registry/johnkattenhorn-docmost-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/johnkattenhorn-docmost-mcp"><img src="https://mcptrustchecker.com/registry/johnkattenhorn-docmost-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/johnkattenhorn-docmost-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 @johnkattenhorn/docmost-mcp --online

Use the free API → How scoring works

Other implementations of Docmost 3

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

More in Developer Tools