Evernote (verygoodplugins) MCP Server

@verygoodplugins/mcp-evernote npm v2.0.0 Source verified

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

MCP server for Evernote integration with note management and synchronization

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 0 = 99. 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:

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

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 4

low Shell/command execution in packaging/dev tooling (scripts/detect-environment.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/detect-environment.js:10`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: port { execSync } from 'child_process'; export function detectEnvironment() { const env = { isClaudeCode: false,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/detect-environment.js

low Shell/command execution in packaging/dev tooling (scripts/install-to-claude.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/install-to-claude.js:7`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: FileSync, spawn } from 'child_process'; import { readFileSync, existsSync } from 'fs'; import { join } from 'path'; impo

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/install-to-claude.js

low Shell/command execution in packaging/dev tooling (scripts/setup.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/setup.js:7`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: port { execSync } from 'child_process'; import { existsSync } from 'fs'; import { join } from 'path'; import readline fr

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/setup.js

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

"@verygoodplugins/mcp-evernote" 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: node scripts/post-install.js 2>/dev/null || true

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

Location: package @verygoodplugins/mcp-evernote

Tools 29

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

  • evernote_add_resource_to_noteno sensitive capability
  • evernote_connectionno sensitive capability
  • evernote_create_noteno sensitive capability
  • evernote_create_notebookno sensitive capability
  • evernote_create_tagno sensitive capability
  • evernote_delete_noteno sensitive capability
  • evernote_get_noteno sensitive capability
  • evernote_get_notebookno sensitive capability
  • evernote_get_resourceno sensitive capability
  • evernote_get_resource_recognitionno sensitive capability
Show 19 more tools ↓
  • evernote_get_resource_textno sensitive capability
  • evernote_get_tagno sensitive capability
  • evernote_get_user_infono sensitive capability
  • evernote_health_checkno sensitive capability
  • evernote_list_note_resourcesno sensitive capability
  • evernote_list_notebooksno sensitive capability
  • evernote_list_tagsno sensitive capability
  • evernote_patch_noteno sensitive capability
  • evernote_poll_nowno sensitive capability
  • evernote_pollingno sensitive capability
  • evernote_polling_statusno sensitive capability
  • evernote_reconnectno sensitive capability
  • evernote_revoke_authno sensitive capability
  • evernote_search_notesno sensitive capability
  • evernote_start_pollingno sensitive capability
  • evernote_stop_pollingno sensitive capability
  • evernote_update_noteno sensitive capability
  • evernote_update_notebookno sensitive capability
  • evernote_update_tagno sensitive capability

What this scan could not see

Versions 2

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
v2.0.0 latest A 99/100 4 1.13.0 2026-09-07
v1.2.3 A 96/100 5 1.12.1 2026-08-10

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

Use the free API → How scoring works

Other implementations of Evernote 2

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

More in Web, Search & Scraping