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

io.github.sumanaddanki/suma-memory

NPM · SUMA-MCP-PROXY · 2 COMPONENTS · SCANNED AUG 3

Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.

+17 this week 61 Trust /100
Trust breakdown (6 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 →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1141 tokens (~163/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

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 · suma-mcp-proxy

# add to Claude Code
claude mcp add sumanaddanki-suma-memory -- npx -y suma-mcp-proxy
# add to Codex CLI
codex mcp add sumanaddanki-suma-memory -- npx -y suma-mcp-proxy
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sumanaddanki-suma-memory": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "suma-mcp-proxy"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sumanaddanki-suma-memory --command npx --arg -y --arg suma-mcp-proxy
# ~/.hermes/config.yaml
mcp_servers:
  sumanaddanki-suma-memory:
    command: "npx"
    args: ["-y", "suma-mcp-proxy"]
// mcp.json
{
  "mcpServers": {
    "sumanaddanki-suma-memory": {
      "command": "npx",
      "args": [
        "-y",
        "suma-mcp-proxy"
      ]
    }
  }
}
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.

  • 2 Aug 26 +42
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Security disclosure: fail → unverified functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → good functional
    • Licence: MIT functional
  • 31 Jul 26 −25
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 44

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 7 exposed · ~1,141 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.

Tool Tokens
suma_clean ~49

Wipe all data for this org. DESTRUCTIVE — requires confirmation. Args: confirm: Must be true to proceed (required)

NameTypeReqDescription
confirmbooleanyesMust be true to wipe data

No output schema declared.

No examples provided.

suma_correct ~122

Correct an incorrect node — preserves audit trail, cleans graph. The node is marked as superseded (never deleted), and all its mentions/entities are cleaned. Use this when you find incorrect information in the knowledge graph. Args: node_id: The node ID to correct (required) reason: Why this node is wrong (required) replacement_text: Correct information to ingest (optional)

NameTypeReqDescription
node_idstringyesNode ID to correct
reasonstringyesWhy this is wrong
replacement_textstringCorrect information (optional)

No output schema declared.

No examples provided.

suma_ingest ~531

Add knowledge to the SUMA graph. The engine accepts any form of input — raw conversational paragraphs, verbatim file excerpts, synthesized factual statements, or compressed semantic summaries. K-WIL gravity (cosine² × decay × harmonic_weight) will rank all nodes correctly regardless of ingestion style. How you drive the engine is determined by your use case, not the engine itself. Provenance tip: always populate source_doc and source_page so retrieved nodes can be traced back to the physical file. The engine stores provenance but does not enforce it. Args: text: The compressed knowledge to store (required) sphere: Category - family, work, friends, health, architecture (optional, auto-classified) extract_relationships: Auto-extract entities (default: true) source_doc: Where this came from — file path, URL, or document title (optional) source_section: Chapter, heading, or function name within the document (optional) source_page: Page number (PDF) or line number (code) (optional) source_type: 'manual'|'file'|'pdf'|'url'|'code' (optional, default: manual) Response fields: node_id: ID of the created or reinforced node status: 'created' | 'merged' (merged = near-duplicate detected by Gate 2) similarity: Cosine similarity score against the nearest existing node (0.0–1.0). Only present when status='merged'. harmonic_weight: Updated harmonic weight of the node after Gate 2 Hebbian reinforcement. Near-duplicates strengthen the existing node instead of creating noise. reinforcement: How much harmonic_weight increased this ingest (e.g. 0.05–0.20). Higher for near-identical content. Only present when status='merged'.

NameTypeReqDescription
extract_relationshipsbooleanExtract entities (default: true)
labelstringShort human-readable title for this node — shown in results, NOT searched (e.g. 'Patent Claim #3', 'Chapter 5 intro')
source_docstringFile path, URL, or document title this came from
source_pageintegerPage number (PDF) or line number (code)
source_sectionstringChapter, heading, or function name within the doc
source_typestringSource type (default: manual)
spherestringCategory (auto-classified if omitted)
textstringyesThe knowledge to store

No output schema declared.

No examples provided.

suma_ping ~22

Health check — verify connection and org. Call once at session start.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

suma_search ~244

Search the knowledge graph using Gravity Well Algorithm. Phases: 1. Entity Strike — find entity by name 2. Neighborhood Expansion — get relationships 3. Evidence Bridge — get related nodes 4. GIN Fallback — full-text search Args: query: Natural language query (required) limit: Max results (default: 10) sphere: Filter by one sphere, OR pass an array for multi-sphere queries (optional) e.g. "work" or ["work", "personal"] historical_search: Set true ONLY when user explicitly asks for past events, older data, or specific date ranges ("last year", "in 2024", "back in March", "what did I do previously"). Suppresses time decay so old nodes surface correctly. Defaults to false.

NameTypeReqDescription
historical_searchbooleanSuppress time decay for explicit historical queries (default: false)
limitintegerMax results (default: 10)
querystringyesNatural language query
sphereFilter by sphere(s) — string or array of strings

No output schema declared.

No examples provided.

suma_stats ~75

Graph statistics and K-WIL token economics for this org. Returns node count, sphere breakdown, queries used, tokens sent vs baseline, compression ratio, and estimated cost saved. The ROI receipt — call this to show the user how much context window budget SUMA has saved them. No arguments needed — reads from the authenticated org.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

suma_talk ~98

Bidirectional memory — search AND learn in one call. Searches for relevant context, optionally stores the message as new knowledge. Args: message: User message (required) learn: Store message as knowledge (default: true) sphere: Category for storage (optional)

NameTypeReqDescription
learnbooleanStore as knowledge (default: true)
messagestringyesUser message
spherestringCategory for storage

No output schema declared.

No examples provided.