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.amirj4m/jamgate

NPM · JAMGATE · SCANNED AUG 3

A neutral memory quality-gate MCP server: save_memory, recall_memory, forget_memory over stdio.

Available components

npm · jamgate 63
+17 this week 63 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 Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 250 tokens (~83/item across 3 items; 3 tools + 0 resources), lean.Pass
  • 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 · jamgate

# add to Claude Code
claude mcp add amirj4m-jamgate -- npx -y jamgate
# add to Codex CLI
codex mcp add amirj4m-jamgate -- npx -y jamgate
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "amirj4m-jamgate": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "jamgate"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add amirj4m-jamgate --command npx --arg -y --arg jamgate
# ~/.hermes/config.yaml
mcp_servers:
  amirj4m-jamgate:
    command: "npx"
    args: ["-y", "jamgate"]
// mcp.json
{
  "mcpServers": {
    "amirj4m-jamgate": {
      "command": "npx",
      "args": [
        "-y",
        "jamgate"
      ]
    }
  }
}
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 +19
    • Known CVEs: partial → unverified ▼ security
    • Malware scan: unverified → pass ▲ 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: pass → unverified ▼ functional
    • Dependency health: partial → unverified ▼ functional
    • Schema quality: unverified → good ▲ functional
  • 1 Aug 26 +38
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −40
    • Malware scan: pass → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 46

    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 — 3 exposed · ~250 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
forget_memory ~28

Delete a stored memory by its id.

NameTypeReqDescription
idstringyesThe memory id to forget.

No output schema declared.

No examples provided.

recall_memory ~48

Recall stored memories about the user relevant to a query.

NameTypeReqDescription
limitnumber—Max results (default 5).
querystring—What to recall. Empty returns the most recent.

No output schema declared.

No examples provided.

save_memory ~174

Save a durable memory about the user through the Jamgate quality gate. Only call this for things worth remembering across sessions — identity, projects, preferences, lasting state — not chatter. Trivial or duplicate input is rejected by the gate.

NameTypeReqDescription
sourcestring—Where this memory came from. Defaults to agent-inferred.
subjectstring—What this memory is about, e.g. 'operating-system', 'location', 'current-project'. If a newer memory shares a subject with an older one, the newer replaces it (time-aware supersession). Strongly reco…
textstringyesThe memory, as a clear standalone statement.
typestring—Which memory layer this belongs to (RULES §4).

No output schema declared.

No examples provided.