Local Memory
Website
Persistent local memory for Claude, Cursor & Codex. 21 MCP tools, hybrid retrieval (BM25 + vector RRF), bi-temporal queries, contradiction detection. SQLite + Knowledge Graph. No cloud, no API keys. npx @studiomeyer/local-memory-mcp
Is Local Memory safe? Promising trust profile, but some evidence still deserves review.
Compare Local Memory
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Local Memory scores 56.7/100 (Grade C), ranked #807 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.8/10; 28% of recent commits are signed; no published advisory affects its latest release (@studiomeyer/local-memory-mcp); last pushed 2026-11-13. Every point is earned from checkable signals — never paid placement. How scoring works →
How Local Memory could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.8 → 71.5 B · #210 of 779
- Raise the OSSF Scorecard from 5.8 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Fuzzing 0 +6.8 → 63.5 C · #335 of 779
- Sign every commit28% signed today +3.6 → 60.3 C · #382 of 779
Chain of custody
Scanners check what the code says. This traces who ships Local Memory and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/studiomeyer-io/local-memory-mcp, MIT, last pushed 2026-11-13. 28% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.8/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies8
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 6Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 8SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 10 -
Published packages Linked, not attested
- npm @studiomeyer/local-memory-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: @studiomeyer/local-memory-mcp 2.4.4. No published advisory affects it (OSV, checked 2026-11-14).
Changes to this chain
- 2026-08-27 OSSF Scorecard: 5.2/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Local Memory’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Local Memory compares in MCP Servers
- #435 OpenROAD MCP 56.8 +0.1
- #436 AEC Model Bridge 56.7 ±0
- #437 Local Memory 56.7 this agent
- #438 Awesome Copilot MCP Server 56.6 −0.1
- #439 Dbmcp 56.6 −0.1
Bars show each HVTrust score; the tick marks Local Memory’s 56.7.
Where the 56.7 comes from
HVTrust dimensions vs the MCP Servers average
56.7 / 100 · 100.0% confidenceLocal Memory MCP Servers average (779 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
48.5 / 100Common questions about Local Memory
Does Local Memory publish package provenance?
Does Local Memory have an OpenSSF Scorecard?
Is Local Memory actively maintained?
What license does Local Memory use?
Are Local Memory's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Local Memory's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Local Memory?
For maintainers
HVTrust scores Local Memory from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/local-memory)
<a href="https://hvtracker.net/agents/local-memory"><img src="https://hvtracker.net/badge/local-memory.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON