Notes by Halo
MCPB · NOTES-BY-HALO-MCP-1.1.0.MCPB
Companion MCP server for Notes by Halo: AI access to your local Markdown notes and tasks.
Available components
Last scanned (18 hours ago)
Scores higher than 70% 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 Security13
- 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
- No install/post-install scripts declared.Pass
- 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 & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 387 tokens (~43/item across 9 items; 8 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_note" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Install scripts
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
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.
- Malware scan in Supply Chain SecurityNo 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.
- Known CVEs in Supply Chain SecurityKnown 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).
- Dependency health in Supply Chain SecurityDependency 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).
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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.
- 14 Nov 26 33
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 21 Nov 2026 · Analysed mcpb/https://github.com/Halo-Software/notes-by-halo-mcp/releases/download/v1.1.0/notes-by-halo-mcp-1.1.0.mcpb@1.1.0
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 →
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 →
create_note ~61
Create a new note with Markdown body and optional color.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Markdown body of the note |
| color | string | – | Note color (Red, Blue, Green, Yellow, Purple, Yellow-Green, Turquoise). Defaults to Red. |
No output schema declared.
No examples provided.
delete_note ~26
Delete a note by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Unique note ID to delete |
No output schema declared.
No examples provided.
get_note ~35
Get full Markdown content, metadata, and extracted task items of a note by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Unique note ID |
No output schema declared.
No examples provided.
list_notes ~64
List all notes with metadata, titles, and task summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Filter by color (Red, Blue, Green, Yellow, Purple, Yellow-Green, Turquoise) |
| limit | number | – | Maximum number of notes to return (default 50) |
No output schema declared.
No examples provided.
list_tasks ~36
List all task checkboxes across all notes with completion status.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Filter tasks by completion status (default: pending) |
No output schema declared.
No examples provided.
search_notes ~40
Search notes using full-text AND search with optional color filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Filter by color |
| query | string | yes | Search keyword(s) |
No output schema declared.
No examples provided.
toggle_task ~55
Toggle the completion checkbox of a specific task within a note.
| Name | Type | Req | Description |
|---|---|---|---|
| noteId | string | yes | ID of the note containing the task |
| taskIndex | number | yes | 0-indexed position of the task checkbox in the note |
No output schema declared.
No examples provided.
update_note ~52
Update the Markdown body and/or color of an existing note.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | New Markdown body content |
| color | string | – | New color |
| id | string | yes | Unique note ID to update |
No output schema declared.
No examples provided.
How do I install the Notes by Halo MCP server?
Notes by Halo 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, 616d6774efc931fce28f694c698be39315f96c99579df0c0f63a394cdb8ff6db; the commands to do that are on this page. If it does not match, do not open it.
mcpb · notes-by-halo-mcp-1.1.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
616d6774efc931fce28f694c698be39315f96c99579df0c0f63a394cdb8ff6db
macOS / Linux
echo "616d6774efc931fce28f694c698be39315f96c99579df0c0f63a394cdb8ff6db notes-by-halo-mcp-1.1.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\notes-by-halo-mcp-1.1.0.mcpb).Hash -eq "616d6774efc931fce28f694c698be39315f96c99579df0c0f63a394cdb8ff6db"
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 Notes by Halo MCP server?
Notes by Halo is an MCP server listed in the public MCP registry as io.github.Halo-Software/notes-by-halo-mcp. Companion MCP server for Notes by Halo: AI access to your local Markdown notes and tasks. This page covers its MCPB bundle (https://github.com/Halo-Software/notes-by-halo-mcp/releases/download/v1.1.0/notes-by-halo-mcp-1.1.0.mcpb).
Is the Notes by Halo MCP server safe to use?
Notes by Halo scores 33 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 Notes by Halo MCP server expose?
Notes by Halo exposes 8 tools: list_notes, get_note, create_note, update_note, delete_note, and 3 more. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.
What licence is the Notes by Halo MCP server under?
Notes by Halo declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the Notes by Halo MCP server?
VerifyMCP ran 12 checks on Notes by Halo, covering Install scripts, Source repository, Provenance, License and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Notes by Halo: Malware scan, Known CVEs, Dependency health and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.