Notemend
NPM · NOTEMEND
Comments pinned on a website, as a queue your coding agent takes, fixes and resolves.
Available components
Last scanned (15 hours ago)
Scores higher than 36% of npm servers
Category Project Management
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 Security100
- 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
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
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
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 1 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 457 tokens (~76/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% 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 current MCP spec version (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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +12
- Known CVEs: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Dependency health: unverified → 1.00 ▲ functional
- Package version: 0.1.23 → 0.1.24 functional
- 15 Oct 26 +32
- Known CVEs: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Dependency health: 1.00 → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 42 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- Package version: 0.1.20 → 0.1.23 functional
- Package version: 0.1.20 → 0.1.22 functional
- Package version: 0.1.20 → 0.1.21 functional
- 14 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.18 → 0.1.20 functional
- 13 Oct 26 0
- Package version: 0.1.16 → 0.1.18 functional
- 12 Oct 26 0
- Package version: 0.1.13 → 0.1.16 functional
- 11 Oct 26 31
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 18 Oct 2026 · Analysed npm/notemend@0.1.24
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| Tree resolution | Complete |
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 →
list_comments List comments ~50
Open comments for the agent, grouped by page, with the element, screen width, device, thread and screenshot paths. all: include resolved ones and those given to people.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | – |
No output schema declared.
No examples provided.
reopen Reopen a comment ~35
Put a resolved comment back in the queue.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The comment id, as list_comments prints it (id N). |
No output schema declared.
No examples provided.
reply Reply in a thread ~51
Answer in a comment's thread without changing its status — a question back, or progress.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The comment id, as list_comments prints it (id N). |
| text | string | yes | – |
No output schema declared.
No examples provided.
resolve Resolve a comment ~84
Mark a comment fixed by the agent, with a note of what changed; it waits for a person to confirm. screenshot: file a picture of the element after the fix (needs Playwright and the dev server running).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The comment id, as list_comments prints it (id N). |
| note | string | – | – |
| screenshot | boolean | – | – |
No output schema declared.
No examples provided.
screenshot Screenshot the element ~82
File a picture of the commented element, at the width the comment was written at, into its thread. before: label it as the state ahead of a fix. Needs Playwright and the dev server running.
| Name | Type | Req | Description |
|---|---|---|---|
| before | boolean | – | – |
| id | integer | yes | The comment id, as list_comments prints it (id N). |
| note | string | – | – |
No output schema declared.
No examples provided.
start Take a comment ~64
Take a comment before fixing it: the thread shows this agent is on it, and another agent asking for it is refused. force: take it anyway.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
| id | integer | yes | The comment id, as list_comments prints it (id N). |
No output schema declared.
No examples provided.
How do I install the Notemend MCP server?
Notemend runs locally as an npm package, launched with npx -y notemend. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · notemend
claude mcp add zharkodv-cmd-notemend -- npx -y notemend
What is the Notemend MCP server?
Notemend is an MCP server listed in the public MCP registry as io.github.zharkodv-cmd/notemend. Comments pinned on a website, as a queue your coding agent takes, fixes and resolves. This page covers its npm package (notemend).
Is the Notemend MCP server safe to use?
Notemend scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. 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 Notemend MCP server expose?
Notemend exposes 6 tools: list_comments, start, reply, resolve, reopen, screenshot. Their descriptions and schemas cost roughly 366 tokens of context every time the server is loaded.
Is the Notemend MCP server still maintained?
Notemend is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.