Lanternote
MCPB · LANTERNOTE-1.22.0.MCPB
Search, read and query large folders of Markdown notes (200,000+). Optional, reversible edits.
Available components
Last scanned (19 hours ago)
Scores higher than 90% of MCPB 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 Security6
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Declares code that runs automatically (postinstall, postinstall (server/package.json)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 949 tokens (~105/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 47. That category is still filling its 30-day observation window: 12 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.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 30 to 40. That category is still filling its 30-day observation window: 9 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.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 30. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +3
- Schema quality: 779 → 949 ▼ functional
- Stability: unverified → 0.20 ▲ functional
- 30 Sept 26 +2
- License: fail → pass ▲ functional
- Licence: PolyForm-Noncommercial-1.0.0 → Apache-2.0 functional
- 28 Sept 26 42
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 17 Oct 2026 · Analysed mcpb/https://github.com/ericthai-labs/lanternote/releases/download/v1.22.0/lanternote-1.22.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 2 scripts
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node scripts/vendor.js && node scripts/notices.js |
| postinstall (server/package.json) | unreviewed | node scripts/vendor.js && node scripts/notices.js |
Background: Why install scripts are a supply-chain risk →
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 →
find_notes ~62
Find notes by name (not content). Words may be in any order; accents optional.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Only inside this folder. |
| limit | integer | – | Maximum results (default 30). |
| name | string | yes | Part of the note name. |
No output schema declared.
No examples provided.
links ~70
Links of a note: the notes it links to and the notes that link to it (backlinks).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum per list (default 100). |
| note | string | yes | The note: a path from the folder root ("Projects/Alpha.md") or just its name ("Alpha"). |
No output schema declared.
No examples provided.
list_tasks ~143
Task lines (- [ ] …) across notes, grouped by note. Due dates come from the task line (📅 2026-10-01 or [due:: 2026-10-01]). Line numbers are 1-based, as set_task expects.
| Name | Type | Req | Description |
|---|---|---|---|
| due_within_days | integer | – | Only tasks due within this many days (overdue ones included). |
| from | string | – | A folder ("Projects") or a tag ("#urgent"). |
| limit | integer | – | Maximum tasks (default 100). |
| status | string | – | open (default), done or all. |
| text | string | – | Only tasks whose text contains this. |
No output schema declared.
No examples provided.
query ~188
Run a Dataview-language query over all notes and get the result as JSON. TABLE f1, f2 FROM "folder" / #tag / [[link]] WHERE … SORT … GROUP BY … LIMIT n; LIST; TASK (task lines: text, status, completed, due, …); CALENDAR <date field>. Fields: front matter, inline key:: value, file.name, file.path, file.mtime, file.tags, file.tasks, … Functions: date(today), dur(7 days), contains, startswith, dateformat, length, … Task line numbers in the result are 1-based, as set_task expects.
| Name | Type | Req | Description |
|---|---|---|---|
| dql | string | yes | The query, e.g. TABLE status, due FROM "Projects" WHERE status != "done" SORT due ASC |
| from_note | string | – | Note used as "this" in the query (optional). |
No output schema declared.
No examples provided.
read_note ~100
Read a note (Markdown, with its front matter). Optionally only the part under one heading. Lines are numbered when with_line_numbers is true (useful before set_task).
| Name | Type | Req | Description |
|---|---|---|---|
| heading | string | – | Only this section (heading text). |
| note | string | yes | The note: a path from the folder root ("Projects/Alpha.md") or just its name ("Alpha"). |
| with_line_numbers | boolean | – | Prefix each line with its number. |
No output schema declared.
No examples provided.
recent ~36
Notes edited most recently.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Only inside this folder. |
| limit | integer | – | How many (default 20). |
No output schema declared.
No examples provided.
search ~56
Full-text search in every note (all words must appear; accents optional). Returns paths with a snippet.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results (default 20, at most 100). |
| query | string | yes | Words to find. |
No output schema declared.
No examples provided.
vault_info ~43
Overview of the notes folder: name, number of notes and links, top folders, most used tags, whether writing is allowed. Call this first to learn the folder layout.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_quote ~170
Check that a quotation or a stated fact really is in a note before citing it. verdict: "exact" (the words are there, ignoring Markdown marks and spacing), "close" (at least 80% of the words and every number are in the matched lines — check the wording) or "not_supported". Numbers in the quotation that are not in the source are listed; always report them rather than citing.
| Name | Type | Req | Description |
|---|---|---|---|
| line | integer | – | 1-based line where the quotation is said to be (optional): only lines around it are checked, and a match elsewhere is reported. |
| note | string | yes | The note: a path from the folder root ("Projects/Alpha.md") or just its name ("Alpha"). |
| quote | string | yes | The text as it will be quoted or stated. |
No output schema declared.
No examples provided.
How do I install the Lanternote MCP server?
Lanternote ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 4360d4e5862898a6dcc4db72c1dc6ccc1d39cf7700a18ae84e4ea90c2fe6363b; the commands to do that are on this page. If it does not match, do not open it.
mcpb · lanternote-1.22.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
4360d4e5862898a6dcc4db72c1dc6ccc1d39cf7700a18ae84e4ea90c2fe6363b
macOS / Linux
echo "4360d4e5862898a6dcc4db72c1dc6ccc1d39cf7700a18ae84e4ea90c2fe6363b lanternote-1.22.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\lanternote-1.22.0.mcpb).Hash -eq "4360d4e5862898a6dcc4db72c1dc6ccc1d39cf7700a18ae84e4ea90c2fe6363b"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the Lanternote MCP server?
Lanternote is an MCP server listed in the public MCP registry as io.github.ericthai-labs/lanternote. Search, read and query large folders of Markdown notes (200,000+). Optional, reversible edits. This page covers its MCPB bundle (https://github.com/ericthai-labs/lanternote/releases/download/v1.22.0/lanternote-1.22.0.mcpb).
Is the Lanternote MCP server safe to use?
Lanternote scores 53 out of 100 on VerifyMCP. 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 Lanternote MCP server expose?
Lanternote exposes 9 tools: vault_info, search, find_notes, read_note, verify_quote, and 4 more. Their descriptions and schemas cost roughly 868 tokens of context every time the server is loaded.
What licence is the Lanternote MCP server under?
Lanternote declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.