WhyNote
NPM · WHY-NOTE-MCP · SCANNED AUG 19
Read-only search, todo listing, and daily note access for a WhyNote account
Available components
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 →
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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 153 tokens (~38/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
- 43% of tool parameters carry a description.Partial
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · why-note-mcp
claude mcp add coooolinz-why-note -- npx -y why-note-mcp
codex mcp add coooolinz-why-note -- npx -y why-note-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"coooolinz-why-note": {
"type": "local",
"command": [
"npx",
"-y",
"why-note-mcp"
],
"enabled": true
}
}
} openclaw mcp add coooolinz-why-note --command npx --arg -y --arg why-note-mcp
mcp_servers:
coooolinz-why-note:
command: "npx"
args: ["-y", "why-note-mcp"] {
"mcpServers": {
"coooolinz-why-note": {
"command": "npx",
"args": [
"-y",
"why-note-mcp"
]
}
}
} 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.
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 11 Aug 26 63
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 19 Aug 2026 · Analysed npm/why-note-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
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.
read_day ~32
Read one day's full note body and etag.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Calendar date in YYYY-MM-DD form. |
No output schema declared.
No examples provided.
recent_days ~48
Read existing note days on one side of an anchor, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor | string | yes | Inclusive YYYY-MM-DD anchor. |
| dir | string | yes | – |
| limit | integer | yes | – |
No output schema declared.
No examples provided.
search ~42
Search note lines using the same case-insensitive substring scan as the web app.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
| q | string | yes | Substring to search for. |
No output schema declared.
No examples provided.
todos ~31
List todo items with done, age, and overdue fields from the note service.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDone | boolean | – | – |
No output schema declared.
No examples provided.