Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.VineetV2/peon-mem

NPM · PEON-MEM

Local-first memory brain for AI coding agents: hooks capture sessions, beliefs injected per prompt.

Available components

0 this week 78 Trust /100

Last scanned (8 hours ago)

Scores higher than 58% of npm servers

Category Memory and Knowledge

Trust breakdown (7 categories)

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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Changelog

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.

  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Package version: 1.0.7 → 1.0.9 functional
  • 26 Oct 26 0
    • Package version: 1.0.7 → 1.0.9 functional
  • 25 Oct 26 0
    • Stability: 0.97 → pass security
  • 24 Oct 26 0
    • Stability: pass → 0.97 functional
  • 18 Oct 26 0
    • Stability: 0.97 → pass security
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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/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 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~750 tokens

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 →

Tool Tokens
build_injection ~55

Build a redacted context injection from project and global memory with selection explanations.

NameTypeReqDescription
includeInactiveboolean––
maxCharsnumber––
projectPathstringyes–
querystring––

No output schema declared.

No examples provided.

end_session ~26

End a Peon session and update brain files.

NameTypeReqDescription
sessionIdstringyes–

No output schema declared.

No examples provided.

evaluate_project ~42

Evaluate recall, coverage, noise, and cost for a Peon project memory folder.

NameTypeReqDescription
expectedMemoriesarray––
projectPathstringyes–

No output schema declared.

No examples provided.

get_context ~40

Return project brain context from Peon memory.

NameTypeReqDescription
maxCharsnumber––
projectPathstringyes–
querystring––

No output schema declared.

No examples provided.

import_global_memory ~33

Import global-scoped memory records from a project brain into the global memory store.

NameTypeReqDescription
projectPathstringyes–

No output schema declared.

No examples provided.

inspect_brain ~51

Return a compact summary of a project's brain: record counts by status and the prompt injection preview.

NameTypeReqDescription
maxCharsnumber––
projectPathstringyes–
querystring––

No output schema declared.

No examples provided.

maybe_process_memory ~49

Apply Peon's automatic cost-aware processing policy and process only when the gate says to run.

NameTypeReqDescription
forceboolean––
projectPathstringyes–
triggerstringyes–

No output schema declared.

No examples provided.

process_memory ~38

Run gated Peon AI processing for a project and update structured brain files.

NameTypeReqDescription
projectPathstringyes–
reasonstring––

No output schema declared.

No examples provided.

quality_report ~42

Inspect Peon memory quality signals: duplicates, conflicts, stale records, and promotions.

NameTypeReqDescription
projectPathstringyes–
staleAfterDaysnumber––

No output schema declared.

No examples provided.

query_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.

NameTypeReqDescription
excludeProjectPathstring––
limitnumber––
projectPathstring––
querystringyes–

No output schema declared.

No examples provided.

record_event ~44

Record a structured Peon memory event such as a decision or preference.

NameTypeReqDescription
contentstringyes–
sessionIdstringyes–
typestringyes–

No output schema declared.

No examples provided.

record_message ~44

Record a user, assistant, or system message into Peon memory.

NameTypeReqDescription
contentstringyes–
rolestringyes–
sessionIdstringyes–

No output schema declared.

No examples provided.

remember_global ~35

Upsert a global Peon memory record for cross-project reuse.

NameTypeReqDescription
memoryobjectyes–
sourceobject––

No output schema declared.

No examples provided.

search_global_memory ~38

Search cross-project global Peon memory.

NameTypeReqDescription
querystring––
statusstring––
typestring––

No output schema declared.

No examples provided.

search_memory ~54

Search structured Peon memory; returns a compact ranked list with one-line reasons.

NameTypeReqDescription
limitnumber––
maxCharsnumber––
projectPathstringyes–
querystringyes–

No output schema declared.

No examples provided.

start_session ~40

Start a Peon memory session for a project.

NameTypeReqDescription
clientstringyes–
cwdstring––
projectPathstringyes–

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add vineetv2-peon-mem -- npx -y peon-mem
Common questions

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 78 out of 100 on VerifyMCP. We found no known CVEs affecting 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.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 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.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.