Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Samsung Notes

NPM · SAMSUNG-NOTES-MCP

Read Samsung Notes: typed text, tables, handwritten pages, photos and PDFs. Never changes a note.

Available components

+3 this week 89 Trust /100

Last scanned (11 hours ago)

Scores higher than 93% of npm servers

Category Productivity and Notes

Trust breakdown (7 categories)

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 Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 110 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Mhemd139/Samsung_Notes). View diagnostics → Pass
  • Clear OSI-approved license (GPL-3.0-only).Pass
  • Actively maintained (last published 21 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1483 tokens (~247/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 90% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Supply Chain Security rose 1.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +4
    • Stability: unverified → 0.30 ▲ functional
  • 17 Oct 26 0
    • Package version: 0.1.4 → 0.1.5 functional
Diagnostics

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 5 Nov 2026 · Analysed npm/samsung-notes-mcp@0.1.5

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 Mhemd139/Samsung_Notes
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Mhemd139/Samsung_Notes/.github/workflows/release.yml@refs/tags/v0.1.5
Rekor log index 3248784963
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:1effe9ede829d17d34e8f46cc4e643308a9f08e642f7ebc30e9f777ab1e49e15bdfb36dd4e2db9ef5243377483e32bc576a94881e350a6ffa7b070143

Background: How many MCP packages publish verified provenance →

Dependencies 110 packages
Packages resolved 110
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~809 tokens

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 →

Tool Tokens
get_attachment ~183

Open a photo or PDF attached to a note, such as an invoice, receipt or scan. Photos come back as images; PDFs as text, plus images of pages without a text layer. Very tall photos and pages come in overlapping parts: read them all before taking figures, and count a repeated line once.

NameTypeReqDescription
as_imagesboolean–PDF only: also send images of pages that have text.
filestringyesAttachment file name from read_note or list_notes.
idstringyesNote id from list_notes.
pagesarray–PDF only: page numbers to read, starting at 1. Default: the first 5.
partinteger–For very tall photos and PDF pages: which part to show, starting at 1. For a PDF, ask for one page at a time: pages=[N].

No output schema declared.

No examples provided.

get_page_image ~99

See one page as an image. Use it for handwriting, drawings and layout, which read_note's text leaves out. Very tall pages come in overlapping parts: read them all, and count a repeated line once.

NameTypeReqDescription
idstringyesNote id from list_notes.
pageintegeryesPage number, starting at 1.
partinteger–For very tall pages: which part to show, starting at 1.

No output schema declared.

No examples provided.

list_notes ~224

Find notes: newest first, filtered by words, folder, modified dates, attachments or handwriting. Returns note ids for the other tools, and next_offset while more remain.

NameTypeReqDescription
folderstring–Folder name from notes_overview, e.g. "Invoices". Includes subfolders. Use "(no folder)" for notes outside folders.
has_attachmentsboolean–true: only notes with photos or PDFs. false: only notes without.
has_handwritingboolean–true: only notes with handwriting or drawings. false: only notes without.
limitinteger––
modified_afterstring–Only notes last edited on or after this day, YYYY-MM-DD. Not the date written on an invoice inside the note.
modified_beforestring–Only notes last edited on or before this day, YYYY-MM-DD. Not the date written on an invoice inside the note.
offsetinteger––
querystring–Words to find in titles and typed text. Every word must appear. Handwriting isn't searched.

No output schema declared.

No examples provided.

notes_overview ~39

Start here. Shows where notes are read from, every folder with its note count, totals, and any problems such as locked or unreadable notes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_note ~48

Read one note: title, folder, dates, pages, attachment list, typed text with tables, and which pages hold handwriting or drawings.

NameTypeReqDescription
idstringyesNote id from list_notes.

No output schema declared.

No examples provided.

save_attachments ~216

Save copies of photos and PDFs attached to notes, such as invoices, receipts and scans, into a folder inside the user's Save folder, under names you choose. Use it only when the user asks to save, collect or organise files. Notes are never changed and no file is overwritten: a taken name gets “ (2)”, and a file whose contents are already in the folder is skipped, so repeating a call is safe. With check_only=true nothing is written: it says which files are already there, so a continued job skips them without opening them.

NameTypeReqDescription
check_onlyboolean–Write nothing; only say which files are already in the folder. Use it before opening files to save, and when continuing an earlier job.
folderstringyesFolder inside the Save folder, e.g. “Invoices 2025” or “Invoices/2025”. A relative name, not a full path; created when the first file is saved.
itemsarrayyesFiles to save, up to 50.

No output schema declared.

No examples provided.

Install

How do I install the Samsung Notes MCP server?

Samsung Notes runs locally as an npm package, launched with npx -y samsung-notes-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · samsung-notes-mcp

# add to Claude Code
claude mcp add mhemd139-samsung-notes -- npx -y samsung-notes-mcp
Common questions

What is the Samsung Notes MCP server?

Samsung Notes is an MCP server listed in the public MCP registry as io.github.Mhemd139/samsung-notes. Read Samsung Notes: typed text, tables, handwritten pages, photos and PDFs. Never changes a note. This page covers its npm package (samsung-notes-mcp).

Is the Samsung Notes MCP server safe to use?

Samsung Notes scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.

What tools does the Samsung Notes MCP server expose?

Samsung Notes exposes 6 tools: notes_overview, list_notes, read_note, get_page_image, get_attachment, save_attachments. Their descriptions and schemas cost roughly 809 tokens of context every time the server is loaded.

Is the Samsung Notes MCP server still maintained?

Samsung Notes is still listed as active in the MCP registry. We last reached this channel on 5 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 Samsung Notes MCP server under?

Samsung Notes declares the GPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.