io.github.VineetV2/peon-mem
NPM · PEON-MEM · SCANNED SEP 20
Local-first memory brain for AI coding agents: hooks capture sessions, beliefs injected per prompt.
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 → Why this is hard to score →
Supply Chain Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
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 Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 750 tokens (~46/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
How do I install the io.github.VineetV2/peon-mem MCP server?
io.github.VineetV2/peon-mem runs locally as an npm package, launched with npx -y peon-mem. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · peon-mem
claude mcp add vineetv2-peon-mem -- npx -y peon-mem
{
"mcpServers": {
"vineetv2-peon-mem": {
"command": "npx",
"args": [
"-y",
"peon-mem"
]
}
}
} {
"servers": {
"vineetv2-peon-mem": {
"command": "npx",
"args": [
"-y",
"peon-mem"
]
}
}
} codex mcp add vineetv2-peon-mem -- npx -y peon-mem
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vineetv2-peon-mem": {
"type": "local",
"command": [
"npx",
"-y",
"peon-mem"
],
"enabled": true
}
}
} openclaw mcp add vineetv2-peon-mem --command npx --arg -y --arg peon-mem
mcp_servers:
vineetv2-peon-mem:
command: "npx"
args: ["-y", "peon-mem"] {
"McpServers": {
"vineetv2-peon-mem": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"peon-mem"
]
}
}
} assistant mcp add vineetv2-peon-mem -t stdio -c npx -a -y peon-mem
{
"mcpServers": {
"vineetv2-peon-mem": {
"command": "npx",
"args": [
"-y",
"peon-mem"
]
}
}
} 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 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 18 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Sept 26 +25
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.84 ▲ functional
- 11 Sept 26 +11
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- Known CVEs: 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
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → 0.84 ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- Package version: 1.0.7 → 1.0.9 functional
- 10 Sept 26 −10
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.84 → unverified ▼ functional
- Package version: 1.0.6 → 1.0.7 functional
- 2 Sept 26 0
- Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
- Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan. security
- Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
- 1 Sept 26 0
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 1.0.4 → 1.0.6 functional
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 20 Sept 2026 · Analysed npm/peon-mem@1.0.9
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
build_injection Build Peon Context Injection ~55
Build a redacted context injection from project and global memory with selection explanations.
| Name | Type | Req | Description |
|---|---|---|---|
| includeInactive | boolean | – | – |
| maxChars | number | – | – |
| projectPath | string | yes | – |
| query | string | – | – |
No output schema declared.
No examples provided.
end_session End Peon Session ~26
End a Peon session and update brain files.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | – |
No output schema declared.
No examples provided.
evaluate_project Evaluate Peon Project Memory ~42
Evaluate recall, coverage, noise, and cost for a Peon project memory folder.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedMemories | array | – | – |
| projectPath | string | yes | – |
No output schema declared.
No examples provided.
get_context Get Peon Context ~40
Return project brain context from Peon memory.
| Name | Type | Req | Description |
|---|---|---|---|
| maxChars | number | – | – |
| projectPath | string | yes | – |
| query | string | – | – |
No output schema declared.
No examples provided.
import_global_memory Import Global Peon Memory ~33
Import global-scoped memory records from a project brain into the global memory store.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | yes | – |
No output schema declared.
No examples provided.
inspect_brain Inspect Peon Brain ~51
Return a compact summary of a project's brain: record counts by status and the prompt injection preview.
| Name | Type | Req | Description |
|---|---|---|---|
| maxChars | number | – | – |
| projectPath | string | yes | – |
| query | string | – | – |
No output schema declared.
No examples provided.
maybe_process_memory Maybe Process Peon Memory ~49
Apply Peon's automatic cost-aware processing policy and process only when the gate says to run.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
| projectPath | string | yes | – |
| trigger | string | yes | – |
No output schema declared.
No examples provided.
process_memory Process Peon Memory ~38
Run gated Peon AI processing for a project and update structured brain files.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
quality_report Peon Quality Report ~42
Inspect Peon memory quality signals: duplicates, conflicts, stale records, and promotions.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | yes | – |
| staleAfterDays | number | – | – |
No output schema declared.
No examples provided.
query_projects Recall Across Projects ~119
Recall relevant beliefs from OTHER Peon projects on demand. Peon memory is isolated per project by default; call this when the user explicitly asks about another project (e.g. 'what did we decide in project Y about auth?'). Omit projectPath to search every known project; pass it to target one. Set excludeProjectPath to the current project so you only get other projects' beliefs.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeProjectPath | string | – | – |
| limit | number | – | – |
| projectPath | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
record_event Record Event ~44
Record a structured Peon memory event such as a decision or preference.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| sessionId | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
record_message Record Message ~44
Record a user, assistant, or system message into Peon memory.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| role | string | yes | – |
| sessionId | string | yes | – |
No output schema declared.
No examples provided.
remember_global Remember Global Memory ~35
Upsert a global Peon memory record for cross-project reuse.
| Name | Type | Req | Description |
|---|---|---|---|
| memory | object | yes | – |
| source | object | – | – |
No output schema declared.
No examples provided.
search_global_memory Search Global Peon Memory ~38
Search cross-project global Peon memory.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
| status | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
search_memory Search Peon Memory ~54
Search structured Peon memory; returns a compact ranked list with one-line reasons.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| maxChars | number | – | – |
| projectPath | string | yes | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
start_session Start Peon Session ~40
Start a Peon memory session for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
| cwd | string | – | – |
| projectPath | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.VineetV2/peon-mem MCP server?
io.github.VineetV2/peon-mem is an MCP server listed in the public MCP registry as io.github.VineetV2/peon-mem. Local-first memory brain for AI coding agents: hooks capture sessions, beliefs injected per prompt. This page covers its npm package (peon-mem).
Is the io.github.VineetV2/peon-mem MCP server safe to use?
io.github.VineetV2/peon-mem scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.VineetV2/peon-mem MCP server expose?
io.github.VineetV2/peon-mem exposes 16 tools: start_session, record_message, record_event, end_session, get_context, and 11 more. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.
Is the io.github.VineetV2/peon-mem MCP server still maintained?
io.github.VineetV2/peon-mem is still listed as active in the MCP registry. We last reached this channel on 20 September 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.VineetV2/peon-mem MCP server under?
io.github.VineetV2/peon-mem declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.