Is Local Memory safe to use?

Local Memory has an HVTrust score of 57.3/100 (Grade C), ranked #528 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Local Memory?

Local Memory scores 57.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 12 GitHub stars and is categorized under MCP Servers.

Local Memory

studiomeyer-io/local-memory-mcp

Persistent local memory for Claude, Cursor & Codex. 21 MCP tools, hybrid retrieval (BM25 + vector RRF), bi-temporal quer

MCP Servers TypeScript Grade C Listed MIT

57.3/100

Rank #528 of 1320

Compare Local Memory

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-04 · 0d ago

Recent change

Grade Changed +8

Is Local Memory safe? Local Memory scores 57.3/100 (Grade C), ranked #528 of 1320 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.2/10; 20% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#239 SearXNG HTTP MCP — 57.4 (C) → #240 Pagerduty MCP Server — 57.3 (C) → #242 Qdrant MCP Server — 57.3 (C) → #243 Rust MCP Sdk — 57.2 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 512 spots (#1038 → #526)

2026-09-03

HVTrust Changed

HVTrust up 19.6pts (37.3 → 56.9)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.2/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Local Memory View MCP Servers Report missing data

50.0

Activity sub-score · out of 100

#241

In MCP Servers

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

2026-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-09-04

today

Commits (4 wk)

Downloads (7d)

117

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #526

Analysis

HVTrust Dimensions vs MCP Servers

57.3 / 100 · 100.0% confidence

Local Memory MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.5 / 25

2.0 below avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.9 / 17

1.1 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

16.7 / 20

4.5 above avg 12.2

AdoptionLog-scaled stars · package downloads

5.4 / 20

0.8 below avg 6.2

Activity Inputs

50.0 / 100

StarsRepository reach

6.7 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

14.7 / 25

CommunityFork signal

3.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.2 / 10

OpenSSF Scorecard · scanned Aug 27, 2026

Signed Commits

20%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 3

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 5

Is Local Memory safe?

Local Memory has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Local Memory publish package provenance?

No published build provenance is currently detected for Local Memory. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Local Memory have an OpenSSF Scorecard?

Local Memory has an OpenSSF Scorecard score of 5.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Local Memory actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Local Memory use?

Local Memory ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Local Memory's commits signed?

19% of the last 100 commits to Local Memory are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Scored in HVTrust

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 Server Support

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 512 spots (#1038 → #526)

2026-09-03

HVTrust Changed

HVTrust up 19.6pts (37.3 → 56.9)

2026-09-02

Rank Moved

Rank dropped 47 spots (#991 → #1038)

2026-09-01

Rank Moved

Rank dropped 32 spots (#959 → #991)

2026-08-31

Rank Moved

Rank dropped 46 spots (#913 → #959)

2026-08-30

Rank Moved

Rank dropped 42 spots (#871 → #913)

2026-08-29

Rank Moved

Rank dropped 47 spots (#824 → #871)

2026-08-28

Rank Moved

Rank dropped 26 spots (#798 → #824)

2026-08-27

Scorecard Added

OSSF Scorecard: 5.2/10

2026-08-27

Rank Moved

Rank rose 352 spots (#1150 → #798)

2026-08-27

HVTrust Changed

HVTrust up 17.9pts (19.8 → 37.7)

2026-08-26

Rank Moved

Rank dropped 59 spots (#1091 → #1150)

2026-08-24

Rank Moved

Rank dropped 10 spots (#1081 → #1091)

2026-08-21

Rank Moved

Rank rose 16 spots (#1098 → #1082)

2026-08-20

Rank Moved

Rank dropped 11 spots (#1087 → #1098)

2026-08-17

Rank Moved

Rank rose 18 spots (#1107 → #1089)

2026-08-16

Rank Moved

Rank dropped 34 spots (#1073 → #1107)

2026-08-10

Rank Moved

Rank dropped 56 spots (#1019 → #1075)

2026-08-08

Newly Listed

First tracked at rank #1030

GitHub → npm: @studiomeyer/local-memory-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/local-memory.svg)](https://hvtracker.net/agents/local-memory)
            
HTML:
            <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

Data sources
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.3 · Raw JSON