Joplin (Lyonk71) MCP Server

joplin-mcp npm v0.2.2 Source verified

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

Model Context Protocol (MCP) server for Joplin note-taking app

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 99 − 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 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 99 − 3 = 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

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

low Package runs install-time scripts (postinstall)MTC-SUP-010

"joplin-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: ./scripts/setup-husky.sh

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package joplin-mcp

Tools 32

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

  • download_attachmentingests untrusted input
  • add_tags_to_noteno sensitive capability
  • append_to_noteno sensitive capability
  • create_noteno sensitive capability
  • create_notebookno sensitive capability
  • delete_noteno sensitive capability
  • delete_notebookno sensitive capability
  • delete_resourceno sensitive capability
  • delete_tagno sensitive capability
  • get_noteno sensitive capability
Show 22 more tools ↓
  • get_note_attachmentsno sensitive capability
  • get_notebook_by_idno sensitive capability
  • get_notebook_notesno sensitive capability
  • get_notes_by_tagno sensitive capability
  • get_resource_metadatano sensitive capability
  • get_resource_notesno sensitive capability
  • get_revisionno sensitive capability
  • get_tag_by_idno sensitive capability
  • list_all_notesno sensitive capability
  • list_all_resourcesno sensitive capability
  • list_all_revisionsno sensitive capability
  • list_notebooksno sensitive capability
  • list_tagsno sensitive capability
  • move_note_to_notebookno sensitive capability
  • prepend_to_noteno sensitive capability
  • remove_tags_from_noteno sensitive capability
  • rename_tagno sensitive capability
  • search_notesno sensitive capability
  • update_noteno sensitive capability
  • update_notebookno sensitive capability
  • update_resourceno sensitive capability
  • upload_attachmentno 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
v0.2.2 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/joplin-mcp-2/badge.svg)](https://mcptrustchecker.com/registry/joplin-mcp-2)
HTML
<a href="https://mcptrustchecker.com/registry/joplin-mcp-2"><img src="https://mcptrustchecker.com/registry/joplin-mcp-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/joplin-mcp-2/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 joplin-mcp --online

Use the free API → How scoring works

Other implementations of Joplin 4

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

More in Productivity & Workflow