Memory (jerrysv) MCP Server

@jerrysv/memory-mcp-server npm v1.0.2

Published by @jerrysv — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for LLM long-term memory storage and recall

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 22

Each tool and what it can reach — statically extracted from the published source.

  • add_memoryno sensitive capability
  • add_relationshipno sensitive capability
  • create_forkno sensitive capability
  • create_fork_at_timeno sensitive capability
  • create_snapshotno sensitive capability
  • delete_forkno sensitive capability
  • delete_memoryno sensitive capability
  • get_due_memoriesno sensitive capability
  • get_memoryno sensitive capability
  • get_related_memoriesno sensitive capability
Show 12 more tools ↓
  • get_relationshipsno sensitive capability
  • get_statsno sensitive capability
  • get_store_snapshotno sensitive capability
  • list_forksno sensitive capability
  • list_memoriesno sensitive capability
  • list_snapshotsno sensitive capability
  • rebuild_indexesno sensitive capability
  • remove_relationshipno sensitive capability
  • restore_snapshotno sensitive capability
  • search_memoriesno sensitive capability
  • update_memoryno sensitive capability
  • verify_integrityno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.2 latest A 98/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/jerrysv-memory-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/jerrysv-memory-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/jerrysv-memory-mcp-server"><img src="https://mcptrustchecker.com/registry/jerrysv-memory-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/jerrysv-memory-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @jerrysv/memory-mcp-server --online

Use the free API → How scoring works

Other implementations of Memory 38

Independent packages implementing the same tool, scanned with the same engine. Compare all 39 side by side →

More in Developer Tools