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.parallelromb/smara

NPM · @SMARA/MCP-SERVER · SCANNED SEP 20

Persistent cross-platform memory for AI agents with Ebbinghaus decay scoring.

Available components

0 this week 80 Trust /100
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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 695 tokens (~139/item across 5 items; 5 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; "delete_memory" implies "delete" 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 6 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
Install

How do I install the io.github.parallelromb/smara MCP server?

io.github.parallelromb/smara runs locally as an npm package, launched with npx -y @smara/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @smara/mcp-server

# add to Claude Code
claude mcp add parallelromb-smara -- npx -y @smara/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "parallelromb-smara": {
      "command": "npx",
      "args": [
        "-y",
        "@smara/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "parallelromb-smara": {
      "command": "npx",
      "args": [
        "-y",
        "@smara/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add parallelromb-smara -- npx -y @smara/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "parallelromb-smara": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@smara/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add parallelromb-smara --command npx --arg -y --arg @smara/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  parallelromb-smara:
    command: "npx"
    args: ["-y", "@smara/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "parallelromb-smara": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@smara/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add parallelromb-smara -t stdio -c npx -a -y @smara/mcp-server
// mcp.json
{
  "mcpServers": {
    "parallelromb-smara": {
      "command": "npx",
      "args": [
        "-y",
        "@smara/mcp-server"
      ]
    }
  }
}
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.

  • 19 Sept 26 +1

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

  • 18 Sept 26 −3
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified functional
  • 16 Sept 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.

  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@smara/mcp-server@2.0.2

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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~386 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
delete_memory ~36

Delete a specific memory by ID. Use when a user asks to forget something.

NameTypeReqDescription
idstringyesThe memory ID to delete

No output schema declared.

No examples provided.

get_usage ~29

Check current memory usage — plan, limits, and how many memories are stored. Useful for monitoring quota.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_user_context ~111

Retrieve a pre-formatted context string for a user, ready to inject into an LLM system prompt. Ranked by Temporal Memory Scoring. Can be called without a query to get the most important recent memories.

NameTypeReqDescription
namespacestringMemory namespace (default: from env or 'default')
qstringOptional query to focus the context on a topic
top_nnumberNumber of top memories to include
user_idstringyesUser to get context for

No output schema declared.

No examples provided.

search_memories ~86

Semantic search across stored memories for a user. Ranked by Temporal Memory Scoring — balances semantic relevance with memory freshness and importance.

NameTypeReqDescription
limitnumberMax results to return
namespacestringMemory namespace (default: from env or 'default')
qstringyesNatural language search query
user_idstringyesUser to search memories for

No output schema declared.

No examples provided.

store_memory ~124

Store a fact or preference about a user. Smara handles deduplication and contradiction detection automatically. Use importance 0.1-0.3 for trivia, 0.5 for general facts, 0.7-1.0 for critical preferences.

NameTypeReqDescription
factstringyesThe fact or preference to remember
importancenumberImportance score (0-1). Higher = slower decay.
namespacestringMemory namespace for isolation (default: from env or 'default')
user_idstringyesUnique identifier for the user

No output schema declared.

No examples provided.

Common questions

What is the io.github.parallelromb/smara MCP server?

io.github.parallelromb/smara is an MCP server listed in the public MCP registry as io.github.parallelromb/smara. Persistent cross-platform memory for AI agents with Ebbinghaus decay scoring. This page covers its npm package (@smara/mcp-server).

Is the io.github.parallelromb/smara MCP server safe to use?

io.github.parallelromb/smara 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.parallelromb/smara MCP server expose?

io.github.parallelromb/smara exposes 5 tools: store_memory, search_memories, get_user_context, delete_memory, get_usage. Their descriptions and schemas cost roughly 386 tokens of context every time the server is loaded.

Is the io.github.parallelromb/smara MCP server still maintained?

io.github.parallelromb/smara 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.parallelromb/smara MCP server under?

io.github.parallelromb/smara declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.