Is Mnemoverse Memory safe to use?

Mnemoverse Memory has an HVTrust score of 69.0/100 (Grade B), ranked #350 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Mnemoverse Memory?

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

Mnemoverse Memory

mnemoverse/mcp-memory-server

Hosted persistent memory for AI agents over MCP. Tell it a recalled memory helped or misled, and it re-ranks what comes back next. Shared rooms for multi-agent work. One key or OAuth across Claude Code, Cursor, VS Code and ChatGPT. MIT, in the official MCP Registry.

MCP Servers TypeScript Listed MIT

Is Mnemoverse Memory safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.5 / 10

Provenance None

Signed commits 100%

Last push today

Compare Mnemoverse Memory

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Mnemoverse Memory scores 69.0/100 (Grade B), ranked #350 of 1325 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 6.5/10; 100% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How Mnemoverse Memory compares in MCP Servers

Bars show each HVTrust score; the tick marks Mnemoverse Memory’s 69.0.

Where the 69.0 comes from

HVTrust dimensions vs the MCP Servers average

69.0 / 100 · 100.0% confidence

Mnemoverse Memory MCP Servers average (775 agents)

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

13.1 / 25

2.8 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.0 / 17

1.8 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.0 / 20

7.0 above avg 12.0

AdoptionLog-scaled stars · package downloads

7.1 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-25

Rank Moved

Rank rose 32 spots (#386 → #354)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.5/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.

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

58.7

Activity sub-score · out of 100

#209

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 B 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-26

Activity & Reach

Stars

Forks

Last Push

2026-09-26

today

Commits (4 wk)

Downloads (7d)

632

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲4

was #354

Analysis

Activity Inputs

58.7 / 100

StarsRepository reach

8.5 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

21.9 / 25

CommunityFork signal

3.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.5 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 5

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 4

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 9

Vulnerabilities 10

Common questions about Mnemoverse Memory

Mnemoverse 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 Mnemoverse Memory publish package provenance?

No published build provenance is currently detected for Mnemoverse 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 Mnemoverse Memory have an OpenSSF Scorecard?

Mnemoverse Memory has an OpenSSF Scorecard score of 6.5/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 Mnemoverse Memory actively maintained?

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

What license does Mnemoverse Memory use?

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

Are Mnemoverse Memory's commits signed?

100% of the last 100 commits to Mnemoverse 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

high confidence

Implemented

Mnemoverse Memory appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

Credential signal: API keys or service config markers documented.

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

How this surface has changed

Detected changes to Mnemoverse 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.

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Mnemoverse Memory?

For maintainers

HVTrust scores Mnemoverse 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-25

Rank Moved

Rank rose 32 spots (#386 → #354)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 370 spots (#763 → #393)

2026-09-23

HVTrust Changed

HVTrust up 37.4pts (29.7 → 67.1)

2026-09-22

Newly Listed

First tracked at rank #763

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank rose 19 spots (#443 → #424)

2026-09-18

Rank Moved

Rank rose 15 spots (#456 → #441)

2026-09-16

Grade Changed

Trust grade C → B

2026-09-13

Grade Changed

Trust grade B → C

2026-09-13

Rank Moved

Rank dropped 12 spots (#449 → #461)

2026-09-11

Rank Moved

Rank dropped 11 spots (#431 → #442)

2026-09-09

Rank Moved

Rank dropped 23 spots (#414 → #437)

2026-09-08

Rank Moved

Rank dropped 13 spots (#401 → #414)

2026-09-07

Rank Moved

Rank dropped 38 spots (#363 → #401)

2026-09-06

Rank Moved

Rank dropped 30 spots (#333 → #363)

2026-09-05

Rank Moved

Rank dropped 68 spots (#265 → #333)

2026-09-04

Grade Changed

Trust grade D → B

2026-09-04

Rank Moved

Rank rose 648 spots (#913 → #265)

2026-09-04

HVTrust Changed

HVTrust up 23.1pts (44.3 → 67.4)

2026-09-03

Rank Moved

Rank rose 15 spots (#928 → #913)

2026-09-02

Rank Moved

Rank dropped 55 spots (#873 → #928)

2026-09-01

Rank Moved

Rank dropped 31 spots (#842 → #873)

2026-08-31

Scorecard Added

OSSF Scorecard: 6.3/10

2026-08-31

Rank Moved

Rank rose 327 spots (#1169 → #842)

2026-08-31

HVTrust Changed

HVTrust up 20.2pts (22.0 → 42.2)

2026-08-30

Rank Moved

Rank dropped 26 spots (#1143 → #1169)

2026-08-29

Rank Moved

Rank dropped 37 spots (#1106 → #1143)

2026-08-28

Rank Moved

Rank dropped 25 spots (#1081 → #1106)

2026-08-27

Rank Moved

Rank dropped 16 spots (#1065 → #1081)

2026-08-26

Rank Moved

Rank dropped 84 spots (#981 → #1065)

2026-08-22

Rank Moved

Rank rose 11 spots (#996 → #985)

2026-08-17

Rank Moved

Rank rose 11 spots (#1007 → #996)

2026-08-16

Rank Moved

Rank dropped 24 spots (#983 → #1007)

2026-08-12

Rank Moved

Rank rose 14 spots (#996 → #982)

2026-08-10

Rank Moved

Rank dropped 59 spots (#933 → #992)

2026-08-08

Newly Listed

First tracked at rank #928

GitHub → npm: @mnemoverse/mcp-memory-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mnemoverse-memory.svg)](https://hvtracker.net/agents/mnemoverse-memory)
            
HTML:
            <a href="https://hvtracker.net/agents/mnemoverse-memory"><img src="https://hvtracker.net/badge/mnemoverse-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