io.github.sumanaddanki/suma-memory
NPM · SUMA-MCP-PROXY · 2 COMPONENTS · SCANNED SEP 20
Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.
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 155 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).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 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "suma_clean" implies "wipe" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 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.sumanaddanki/suma-memory MCP server?
io.github.sumanaddanki/suma-memory runs locally as an npm package, launched with npx -y suma-mcp-proxy. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · suma-mcp-proxy
claude mcp add sumanaddanki-suma-memory -- npx -y suma-mcp-proxy
{
"mcpServers": {
"sumanaddanki-suma-memory": {
"command": "npx",
"args": [
"-y",
"suma-mcp-proxy"
]
}
}
} {
"servers": {
"sumanaddanki-suma-memory": {
"command": "npx",
"args": [
"-y",
"suma-mcp-proxy"
]
}
}
} codex mcp add sumanaddanki-suma-memory -- npx -y suma-mcp-proxy
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sumanaddanki-suma-memory": {
"type": "local",
"command": [
"npx",
"-y",
"suma-mcp-proxy"
],
"enabled": true
}
}
} openclaw mcp add sumanaddanki-suma-memory --command npx --arg -y --arg suma-mcp-proxy
mcp_servers:
sumanaddanki-suma-memory:
command: "npx"
args: ["-y", "suma-mcp-proxy"] {
"McpServers": {
"sumanaddanki-suma-memory": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"suma-mcp-proxy"
]
}
}
} assistant mcp add sumanaddanki-suma-memory -t stdio -c npx -a -y suma-mcp-proxy
{
"mcpServers": {
"sumanaddanki-suma-memory": {
"command": "npx",
"args": [
"-y",
"suma-mcp-proxy"
]
}
}
} 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.
- 20 Sept 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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 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.
- 11 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.77 functional
- 9 Sept 26 +1
- Stability: 0.97 → 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 20 Sept 2026 · Analysed npm/suma-mcp-proxy@1.4.0
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 →
suma_clean ~49
Wipe all data for this org. DESTRUCTIVE — requires confirmation. Args: confirm: Must be true to proceed (required)
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must 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)
| Name | Type | Req | Description |
|---|---|---|---|
| node_id | string | yes | Node ID to correct |
| reason | string | yes | Why this is wrong |
| replacement_text | string | – | Correct 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'.
| Name | Type | Req | Description |
|---|---|---|---|
| extract_relationships | boolean | – | Extract entities (default: true) |
| label | string | – | Short human-readable title for this node — shown in results, NOT searched (e.g. 'Patent Claim #3', 'Chapter 5 intro') |
| source_doc | string | – | File path, URL, or document title this came from |
| source_page | integer | – | Page number (PDF) or line number (code) |
| source_section | string | – | Chapter, heading, or function name within the doc |
| source_type | string | – | Source type (default: manual) |
| sphere | string | – | Category (auto-classified if omitted) |
| text | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| historical_search | boolean | – | Suppress time decay for explicit historical queries (default: false) |
| limit | integer | – | Max results (default: 10) |
| query | string | yes | Natural language query |
| sphere | – | – | Filter 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)
| Name | Type | Req | Description |
|---|---|---|---|
| learn | boolean | – | Store as knowledge (default: true) |
| message | string | yes | User message |
| sphere | string | – | Category for storage |
No output schema declared.
No examples provided.
What is the io.github.sumanaddanki/suma-memory MCP server?
io.github.sumanaddanki/suma-memory is an MCP server listed in the public MCP registry as io.github.sumanaddanki/suma-memory. Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session. This page covers its npm package (suma-mcp-proxy).
Is the io.github.sumanaddanki/suma-memory MCP server safe to use?
io.github.sumanaddanki/suma-memory scores 80 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.sumanaddanki/suma-memory MCP server expose?
io.github.sumanaddanki/suma-memory exposes 7 tools: suma_ping, suma_ingest, suma_search, suma_talk, suma_correct, and 2 more. Their descriptions and schemas cost roughly 1,141 tokens of context every time the server is loaded.
Is the io.github.sumanaddanki/suma-memory MCP server still maintained?
io.github.sumanaddanki/suma-memory 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.sumanaddanki/suma-memory MCP server under?
io.github.sumanaddanki/suma-memory declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.