io.github.jordanburke/joplin-mcp-server
NPM · JOPLIN-MCP-SERVER
Search, read, create, edit and sync Joplin notes and notebooks via a headless Joplin sidecar.
Available components
Last scanned (14 hours ago)
Scores higher than 20% of npm servers
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects adm-zip 0.6.0, reached via joplin > @joplin/lib > adm-zip. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 400 of 846 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to jordanburke/joplin-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 83 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Checks we ran (9)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
Checks we could not complete (5)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Nov 26 0
- CVE-2026-27942 affects this package: high ▼ security
- CVE-2026-114102 affects this package: high ▼ security
- CVE-2026-109924 affects this package: high ▼ security
- CVE-2026-41650 affects this package: high ▼ security
- CVE-2026-41907 affects this package: high ▼ security
- CVE-2026-85024 affects this package: high ▼ security
- CVE-2026-111766 affects this package: high ▼ security
- CVE-2026-59871 affects this package: high ▼ security
- CVE-2026-109829 affects this package: high ▼ security
- CVE-2026-126066 affects this package: high ▼ security
- CVE-2026-84933 affects this package: high ▼ security
- CVE-2026-18149 affects this package: high ▼ security
- CVE-2026-116689 affects this package: high ▼ security
- CVE-2026-102282 affects this package: high ▼ security
- CVE-2026-53655 affects this package: high ▼ security
- CVE-2026-109383 affects this package: high ▼ security
- CVE-2026-59873 affects this package: high ▼ security
- CVE-2026-33349 affects this package: high ▼ security
- CVE-2026-67213 affects this package: high ▼ security
- CVE-2026-111755 affects this package: high ▼ security
- CVE-2026-85152 affects this package: high ▼ security
- CVE-2026-73086 affects this package: high ▼ security
- CVE-2026-84947 affects this package: high ▼ security
- CVE-2026-84890 affects this package: high ▼ security
- CVE-2026-24842 affects this package: high ▼ security
- CVE-2026-29786 affects this package: high ▼ security
- CVE-2026-23950 affects this package: high ▼ security
- CVE-2026-73566 affects this package: high ▼ security
- CVE-2026-114112 affects this package: high ▼ security
- CVE-2026-103923 affects this package: high ▼ security
- CVE-2026-92000 affects this package: high ▼ security
- CVE-2026-84375 affects this package: high ▼ security
- GHSA-253c-mchw-3w2r affects this package: high ▼ security
- CVE-2026-48988 affects this package: high ▼ security
- CVE-2026-77301 affects this package: high ▼ security
- CVE-2026-109869 affects this package: high ▼ security
- CVE-2026-59874 affects this package: high ▼ security
- CVE-2026-114103 affects this package: high ▼ security
- CVE-2026-59875 affects this package: high ▼ security
- CVE-2026-111756 affects this package: high ▼ security
- CVE-2026-114113 affects this package: high ▼ security
- CVE-2026-85014 affects this package: high ▼ security
- CVE-2026-26960 affects this package: high ▼ security
- CVE-2023-0842 affects this package: high ▼ security
- CVE-2026-2327 affects this package: high ▼ security
- CVE-2026-31808 affects this package: high ▼ security
- CVE-2026-85008 affects this package: high ▼ security
- CVE-2026-114111 affects this package: high ▼ security
- CVE-2026-18540 affects this package: high ▼ security
- CVE-2021-4306 affects this package: high ▼ security
- CVE-2026-87029 affects this package: high ▼ security
- CVE-2026-118773 affects this package: high ▼ security
- CVE-2026-109841 affects this package: high ▼ security
- CVE-2026-87018 affects this package: high ▼ security
- CVE-2026-111759 affects this package: high ▼ security
- CVE-2021-26920 affects this package: high ▼ security
- CVE-2026-19534 affects this package: high ▼ security
- CVE-2026-33036 affects this package: high ▼ security
- CVE-2026-23745 affects this package: high ▼ security
- CVE-2026-84961 affects this package: high ▼ security
- CVE-2026-17495 affects this package: high ▼ security
- CVE-2026-67214 affects this package: high ▼ security
- CVE-2026-31802 affects this package: high ▼ security
- CVE-2026-114104 affects this package: high ▼ security
- CVE-2026-109932 affects this package: high ▼ security
- 21 Nov 26 0
- CVE-2026-27942 affects this package: high ▼ security
- CVE-2026-114102 affects this package: high ▼ security
- CVE-2026-109924 affects this package: high ▼ security
- CVE-2026-41650 affects this package: high ▼ security
- CVE-2026-41907 affects this package: high ▼ security
- CVE-2026-85024 affects this package: high ▼ security
- CVE-2026-111766 affects this package: high ▼ security
- CVE-2026-59871 affects this package: high ▼ security
- CVE-2026-109829 affects this package: high ▼ security
- CVE-2026-126066 affects this package: high ▼ security
- CVE-2026-84933 affects this package: high ▼ security
- CVE-2026-18149 affects this package: high ▼ security
- CVE-2026-116689 affects this package: high ▼ security
- CVE-2026-102282 affects this package: high ▼ security
- CVE-2026-53655 affects this package: high ▼ security
- CVE-2026-109383 affects this package: high ▼ security
- CVE-2026-59873 affects this package: high ▼ security
- CVE-2026-33349 affects this package: high ▼ security
- CVE-2026-67213 affects this package: high ▼ security
- CVE-2026-111755 affects this package: high ▼ security
- CVE-2026-85152 affects this package: high ▼ security
- CVE-2026-73086 affects this package: high ▼ security
- CVE-2026-84947 affects this package: high ▼ security
- CVE-2026-84890 affects this package: high ▼ security
- CVE-2026-24842 affects this package: high ▼ security
- CVE-2026-29786 affects this package: high ▼ security
- CVE-2026-23950 affects this package: high ▼ security
- CVE-2026-73566 affects this package: high ▼ security
- CVE-2026-114112 affects this package: high ▼ security
- CVE-2026-103923 affects this package: high ▼ security
- CVE-2026-92000 affects this package: high ▼ security
- CVE-2026-84375 affects this package: high ▼ security
- GHSA-253c-mchw-3w2r affects this package: high ▼ security
- CVE-2026-48988 affects this package: high ▼ security
- CVE-2026-77301 affects this package: high ▼ security
- CVE-2026-109869 affects this package: high ▼ security
- CVE-2026-59874 affects this package: high ▼ security
- CVE-2026-114103 affects this package: high ▼ security
- CVE-2026-59875 affects this package: high ▼ security
- CVE-2026-111756 affects this package: high ▼ security
- CVE-2026-114113 affects this package: high ▼ security
- CVE-2026-85014 affects this package: high ▼ security
- CVE-2026-26960 affects this package: high ▼ security
- CVE-2023-0842 affects this package: high ▼ security
- CVE-2026-2327 affects this package: high ▼ security
- CVE-2026-31808 affects this package: high ▼ security
- CVE-2026-85008 affects this package: high ▼ security
- CVE-2026-114111 affects this package: high ▼ security
- CVE-2026-18540 affects this package: high ▼ security
- CVE-2021-4306 affects this package: high ▼ security
- CVE-2026-87029 affects this package: high ▼ security
- CVE-2026-118773 affects this package: high ▼ security
- CVE-2026-109841 affects this package: high ▼ security
- CVE-2026-87018 affects this package: high ▼ security
- CVE-2026-111759 affects this package: high ▼ security
- CVE-2021-26920 affects this package: high ▼ security
- CVE-2026-19534 affects this package: high ▼ security
- CVE-2026-33036 affects this package: high ▼ security
- CVE-2026-23745 affects this package: high ▼ security
- CVE-2026-84961 affects this package: high ▼ security
- CVE-2026-17495 affects this package: high ▼ security
- CVE-2026-67214 affects this package: high ▼ security
- CVE-2026-31802 affects this package: high ▼ security
- CVE-2026-114104 affects this package: high ▼ security
- CVE-2026-109932 affects this package: high ▼ security
- 20 Nov 26 0
- CVE-2026-27942 affects this package: high ▼ security
- CVE-2026-114102 affects this package: high ▼ security
- CVE-2026-109924 affects this package: high ▼ security
- CVE-2026-41650 affects this package: high ▼ security
- CVE-2026-41907 affects this package: high ▼ security
- CVE-2026-85024 affects this package: high ▼ security
- CVE-2026-111766 affects this package: high ▼ security
- CVE-2026-59871 affects this package: high ▼ security
- CVE-2026-109829 affects this package: high ▼ security
- CVE-2026-126066 affects this package: high ▼ security
- CVE-2026-84933 affects this package: high ▼ security
- CVE-2026-18149 affects this package: high ▼ security
- CVE-2026-116689 affects this package: high ▼ security
- CVE-2026-102282 affects this package: high ▼ security
- CVE-2026-53655 affects this package: high ▼ security
- CVE-2026-109383 affects this package: high ▼ security
- CVE-2026-59873 affects this package: high ▼ security
- CVE-2026-33349 affects this package: high ▼ security
- CVE-2026-67213 affects this package: high ▼ security
- CVE-2026-111755 affects this package: high ▼ security
- CVE-2026-85152 affects this package: high ▼ security
- CVE-2026-73086 affects this package: high ▼ security
- CVE-2026-84947 affects this package: high ▼ security
- CVE-2026-84890 affects this package: high ▼ security
- CVE-2026-24842 affects this package: high ▼ security
- CVE-2026-29786 affects this package: high ▼ security
- CVE-2026-23950 affects this package: high ▼ security
- CVE-2026-73566 affects this package: high ▼ security
- CVE-2026-114112 affects this package: high ▼ security
- CVE-2026-103923 affects this package: high ▼ security
- CVE-2026-92000 affects this package: high ▼ security
- CVE-2026-84375 affects this package: high ▼ security
- GHSA-253c-mchw-3w2r affects this package: high ▼ security
- CVE-2026-48988 affects this package: high ▼ security
- CVE-2026-77301 affects this package: high ▼ security
- CVE-2026-109869 affects this package: high ▼ security
- CVE-2026-59874 affects this package: high ▼ security
- CVE-2026-114103 affects this package: high ▼ security
- CVE-2026-59875 affects this package: high ▼ security
- CVE-2026-111756 affects this package: high ▼ security
- CVE-2026-114113 affects this package: high ▼ security
- CVE-2026-85014 affects this package: high ▼ security
- CVE-2026-26960 affects this package: high ▼ security
- CVE-2023-0842 affects this package: high ▼ security
- CVE-2026-2327 affects this package: high ▼ security
- CVE-2026-31808 affects this package: high ▼ security
- CVE-2026-85008 affects this package: high ▼ security
- CVE-2026-114111 affects this package: high ▼ security
- CVE-2026-18540 affects this package: high ▼ security
- CVE-2021-4306 affects this package: high ▼ security
- CVE-2026-87029 affects this package: high ▼ security
- CVE-2026-118773 affects this package: high ▼ security
- CVE-2026-109841 affects this package: high ▼ security
- CVE-2026-87018 affects this package: high ▼ security
- CVE-2026-111759 affects this package: high ▼ security
- CVE-2021-26920 affects this package: high ▼ security
- CVE-2026-19534 affects this package: high ▼ security
- CVE-2026-33036 affects this package: high ▼ security
- CVE-2026-23745 affects this package: high ▼ security
- CVE-2026-84961 affects this package: high ▼ security
- CVE-2026-17495 affects this package: high ▼ security
- CVE-2026-67214 affects this package: high ▼ security
- CVE-2026-31802 affects this package: high ▼ security
- CVE-2026-114104 affects this package: high ▼ security
- CVE-2026-109932 affects this package: high ▼ security
- 19 Nov 26 0
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- CVE-2026-27942 affects this package: high ▼ security
- CVE-2026-114102 affects this package: high ▼ security
- CVE-2026-109924 affects this package: high ▼ security
- CVE-2026-41650 affects this package: high ▼ security
- CVE-2026-41907 affects this package: high ▼ security
- 10 Nov 26 +5
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- 9 Nov 26 −5
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- 24 Oct 26 43
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Nov 2026 · Analysed npm/joplin-mcp-server@2.3.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | jordanburke/joplin-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/jordanburke/joplin-mcp-server/.github/workflows/publish.yml@refs/tags/v2.3.3 |
| Rekor log index | 2656088410 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:668b93f3ee5966dc584c22ae8b95bc68d0322a60eb01bdfc19022549b112f8e13d51beddf67f14eb7436f189262fe82cabad0dd58def9b376cede8de3 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 68 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-7q85-xj36-vmfc | CVE-2026-77301 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-8238-w5pm-2374 | CVE-2026-114102 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-c6fg-446q-cg94 | CVE-2026-114103 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-j5f4-cc29-5x44 | CVE-2026-102282 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-p634-w6r4-rjp2 | CVE-2026-114104 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-rcw4-f5rp-g42v | CVE-2026-92000 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vwc7-r8mq-g2x9 | CVE-2026-76845 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N | no |
| GHSA-j965-2qgj-vjmq | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N | no | |
| GHSA-474x-hrwr-fgx4 | CVE-2026-126066 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-gh4j-gqv2-49f6 | CVE-2026-41650 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-x3cc-x39p-42qx | CVE-2021-26920 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-8gc5-j5rx-235r | CVE-2026-33036 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-fj3w-jwp8-x2g3 | CVE-2026-27942 | low | yes | |
| GHSA-jp2q-39xq-3w4g | CVE-2026-33349 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-5v7r-6r5c-r473 | CVE-2026-31808 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-8r9p-f939-6h3c | CVE-2026-111755 | high | yes | |
| GHSA-mrwp-f3q8-3g9p | CVE-2026-116689 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-q3jh-wrc6-jgq8 | CVE-2026-111756 | high | yes | |
| GHSA-3g3m-2fjr-6pw4 | CVE-2026-118773 | medium | yes | |
| GHSA-pfq8-rq6v-vf5m | CVE-2022-37620 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| GHSA-2883-xcg3-v3hh | CVE-2026-84375 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-238p-pmpm-9mq7 | CVE-2026-103923 | low | yes | |
| GHSA-253c-mchw-3w2r | medium | yes | ||
| GHSA-38c4-r59v-3vqw | CVE-2026-2327 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-6v5v-wf23-fmfq | CVE-2026-48988 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-r7fv-28h4-cvq7 | CVE-2026-111759 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vfgh-jcmw-g37q | CVE-2026-111766 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-4p3w-j4w9-5jqw | CVE-2026-17495 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-28wg-ghj8-5hjv | CVE-2026-67214 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-2v37-7h3g-55p8 | CVE-2026-67213 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-xwg4-73v4-xw9w | CVE-2026-73086 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-f88m-g3jw-g9cj | CVE-2026-114113 | high | yes | |
| GHSA-rgj7-g3m4-5g8c | CVE-2026-114112 | high | yes | |
| GHSA-wq5f-xc86-pv6w | CVE-2026-114111 | high | yes | |
| GHSA-23hp-3jrh-7fpw | CVE-2026-59873 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-34x7-hfp2-rc4v | CVE-2026-24842 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N | yes |
| GHSA-83g3-92jg-28cx | CVE-2026-26960 | high | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N | yes |
| GHSA-8qq5-rm4j-mr97 | CVE-2026-23745 | high | yes | |
| GHSA-8x88-c5mf-7j5w | CVE-2026-59874 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-9ppj-qmqm-q256 | CVE-2026-31802 | high | yes | |
| GHSA-gvwx-54wh-qm9j | CVE-2026-59875 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-qffp-2rhf-9h96 | CVE-2026-29786 | high | yes | |
| GHSA-r292-9mhp-454m | CVE-2026-73566 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-r6q2-hw4h-h46w | CVE-2026-23950 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L | yes |
| GHSA-vmf3-w455-68vh | CVE-2026-53655 | medium | yes | |
| GHSA-w8wr-v893-vjvp | CVE-2026-59871 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-wxgh-8gmr-3qh3 | CVE-2021-4306 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-2gqq-gqf2-x968 | CVE-2026-84947 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-2jfj-6hjv-fm6j | CVE-2026-84933 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-2m5v-pch6-74hx | CVE-2026-109383 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
Showing 50 of 68 vulnerabilities.
Background: What a vulnerability scan can and cannot prove →
Dependencies 400 packages
| Packages resolved | 400 |
|---|---|
| Deprecated | 7 |
| Stale | 156 |
| No linked repository | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the io.github.jordanburke/joplin-mcp-server server?
io.github.jordanburke/joplin-mcp-server runs locally as an npm package, launched with npx -y joplin-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · joplin-mcp-server
claude mcp add jordanburke-joplin-mcp-server -- npx -y joplin-mcp-server
What is the io.github.jordanburke/joplin-mcp-server server?
io.github.jordanburke/joplin-mcp-server is listed in the public MCP registry as io.github.jordanburke/joplin-mcp-server. Search, read, create, edit and sync Joplin notes and notebooks via a headless Joplin sidecar. This page covers its npm package (joplin-mcp-server).
Is the io.github.jordanburke/joplin-mcp-server server safe to use?
io.github.jordanburke/joplin-mcp-server scores 43 out of 100 on VerifyMCP. We recorded 68 known advisories against it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the io.github.jordanburke/joplin-mcp-server server still maintained?
io.github.jordanburke/joplin-mcp-server is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.jordanburke/joplin-mcp-server server under?
io.github.jordanburke/joplin-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.jordanburke/joplin-mcp-server server?
VerifyMCP ran 9 checks on io.github.jordanburke/joplin-mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about io.github.jordanburke/joplin-mcp-server: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.