io.github.paperdavid/manoma
NPM · MANOMA-MCP
MCP server for soul.md — your portable AI identity layer across every LLM.
Available components
Last scanned (3 hours ago)
Scores higher than 58% of npm servers
Category Memory and Knowledge
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency39
- 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
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1307 tokens (~65/item across 20 items; 7 tools + 13 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −3
- Stability: pass → 0.83 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
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/manoma-mcp@0.2.1
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
add_decision Add Decision ~145
Record a decision in /memory/decisions. Appends a timestamped entry to the decisions section of soul.md. This is how the AI helps maintain soul.md as a living document — capturing decisions as they happen during conversation. Args: - decision (string): The decision to record. Be specific about what was chosen and why. - context (string, optional): Additional reasoning or alternatives considered. Returns: Confirmation with the recorded entry.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional additional context or reasoning |
| decision | string | yes | The decision to record (e.g. "Chose Postgres over DynamoDB for billing — need ACID transactions") |
No output schema declared.
No examples provided.
add_lesson Add Lesson ~153
Record a lesson learned in /memory/lessons. Appends a timestamped entry to the lessons section. Captures insights and hard-won knowledge from debugging, incidents, code reviews, reading, or any learning moment. Args: - lesson (string): The lesson to record. Be specific and actionable. - source (string, optional): Where this lesson came from. Returns: Confirmation with the recorded entry.
| Name | Type | Req | Description |
|---|---|---|---|
| lesson | string | yes | The lesson learned (e.g. "Redis SCAN is O(N) — don't use on hot paths without cursor batching") |
| source | string | – | Where the lesson came from (e.g. "production incident", "code review", "reading") |
No output schema declared.
No examples provided.
get_context Get Context ~148
Retrieve the user's identity context for the current or specified mode. Returns all soul.md sections that should be injected for the given mode, as defined by mode_routing in /config. This is the primary way an LLM should bootstrap context about the user. Args: - mode (string, optional): One of work, personal, creative, learning. Defaults to the active_mode in soul.md config. Returns: Combined markdown of all sections relevant to the requested mode, including identity, values, voice, skills, and any mode-specific sections.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Mode to resolve context for (work, personal, creative, learning). Defaults to active_mode from config. |
No output schema declared.
No examples provided.
get_injection Get Injection ~196
Build a smart context injection from soul.md for an LLM system prompt. Unlike get_context which returns raw sections, this runs the full injection algorithm: three-tier priority (always/by_mode/on_trigger), keyword matching for skill domains, person detection, voice dial conversion to behavioral instructions, and token budgeting (2500 max with priority-aware truncation). Use this when assembling the full identity blob for an LLM system prompt. Args: - mode (string, optional): One of work, personal, creative, learning. - message (string, optional): The user's message. Used for trigger matching. Returns: The injection text, token count, matched sections, triggered domains, and mentioned people.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | The user's message. Used for keyword/skill/person triggering. |
| mode | string | – | Mode (work, personal, creative, learning). Defaults to active_mode from config. |
No output schema declared.
No examples provided.
get_skill_depth Get Skill Depth ~115
Retrieve detailed skill information for a specific domain. Searches soul.md skill sections for a matching domain and returns the full detail block including level, years, approach, heuristics, and taste. Args: - skill (string): Skill domain name to look up. Returns: Detailed skill section content if found, or a list of available skills with a suggestion to check skills.summary.
| Name | Type | Req | Description |
|---|---|---|---|
| skill | string | yes | Skill domain to look up (e.g. "backend systems", "observability", "frontend") |
No output schema declared.
No examples provided.
list_sections List Sections ~44
List all available sections in soul.md. Returns a tree-like listing of all sections with their paths, names, metadata, and child sections. Useful for discovering what's in the soul.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_now Update Now ~115
Replace the /now section with current focus and status. The /now section captures what the user is currently working on, thinking about, and prioritizing. This tool replaces it entirely with new content. Args: - content (string): New markdown content for the /now section. Should describe current projects, focus areas, blockers, and priorities. Returns: Confirmation with the new content.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | New content for the /now section. Use markdown. This replaces the entire /now section. |
No output schema declared.
No examples provided.
How do I install the io.github.paperdavid/manoma MCP server?
io.github.paperdavid/manoma runs locally as an npm package, launched with npx -y manoma-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 · manoma-mcp
claude mcp add paperdavid-manoma -- npx -y manoma-mcp
What is the io.github.paperdavid/manoma MCP server?
io.github.paperdavid/manoma is an MCP server listed in the public MCP registry as io.github.paperdavid/manoma. MCP server for soul.md, your portable AI identity layer across every LLM. This page covers its npm package (manoma-mcp).
Is the io.github.paperdavid/manoma MCP server safe to use?
io.github.paperdavid/manoma scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 io.github.paperdavid/manoma MCP server expose?
io.github.paperdavid/manoma exposes 7 tools: get_context, get_injection, get_skill_depth, list_sections, add_decision, and 2 more. Their descriptions and schemas cost roughly 916 tokens of context every time the server is loaded.
Is the io.github.paperdavid/manoma MCP server still maintained?
io.github.paperdavid/manoma 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 io.github.paperdavid/manoma MCP server under?
io.github.paperdavid/manoma declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.