Is MCP AutoMem safe to use?

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

What is the trust score for MCP AutoMem?

MCP AutoMem scores 74.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 65 GitHub stars and is categorized under MCP Servers.

MCP AutoMem

verygoodplugins/mcp-automem

MCP client for AutoMem — give Claude, Cursor, Codex, and other MCP tools durable graph+vector memory across conversations.

MCP Servers TypeScript Listed MIT

Is MCP AutoMem safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.1 / 10

Provenance Attested

Signed commits 100%

Last push 4d ago

Compare MCP AutoMem

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP AutoMem scores 74.1/100 (Grade B), ranked #240 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.1/10; 100% of recent commits are signed; last pushed 2026-09-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP AutoMem compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP AutoMem’s 74.1.

Where the 74.1 comes from

HVTrust dimensions vs the MCP Servers average

74.1 / 100 · 100.0% confidence

MCP AutoMem MCP Servers average (775 agents)

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

18.9 / 25

8.6 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.8 / 17

0.6 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

11.7 / 20

in line with avg 12.0

AdoptionLog-scaled stars · package downloads

7.0 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-25

Rank Moved

Rank dropped 12 spots (#226 → #238)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

Maintainer Checklist

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

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

41.1

Activity sub-score · out of 100

#143

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-22

4 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #238

Analysis

Activity Inputs

41.1 / 100

StarsRepository reach

10.9 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.6 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.1 / 10

OpenSSF Scorecard · scanned Sep 26, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 10

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about MCP AutoMem

MCP AutoMem 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 MCP AutoMem publish package provenance?

Yes. MCP AutoMem's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does MCP AutoMem have an OpenSSF Scorecard?

MCP AutoMem has an OpenSSF Scorecard score of 5.1/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 MCP AutoMem actively maintained?

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

What license does MCP AutoMem use?

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

Are MCP AutoMem's commits signed?

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

MCP AutoMem appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 MCP AutoMem'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain MCP AutoMem?

For maintainers

HVTrust scores MCP AutoMem 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 dropped 12 spots (#226 → #238)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 619 spots (#845 → #226)

2026-09-23

HVTrust Changed

HVTrust up 46.9pts (28.0 → 74.9)

2026-09-23

Activity Score Changed

Activity score down 10pts (55 → 45)

2026-09-22

Newly Listed

First tracked at rank #845

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Grade Changed

Trust grade A → B

2026-09-16

Grade Changed

Trust grade B → A

2026-09-15

Grade Changed

Trust grade A → B

2026-09-07

Grade Changed

Trust grade C → A

2026-09-07

Rank Moved

Rank rose 624 spots (#755 → #131)

2026-09-07

HVTrust Changed

HVTrust up 26.7pts (53.4 → 80.1)

2026-09-06

Rank Moved

Rank dropped 13 spots (#742 → #755)

2026-09-05

Rank Moved

Rank dropped 65 spots (#677 → #742)

2026-09-04

Rank Moved

Rank dropped 52 spots (#625 → #677)

2026-09-03

Rank Moved

Rank rose 38 spots (#663 → #625)

2026-09-02

Rank Moved

Rank dropped 32 spots (#631 → #663)

2026-09-01

Rank Moved

Rank dropped 25 spots (#606 → #631)

2026-08-31

Rank Moved

Rank dropped 31 spots (#575 → #606)

2026-08-29

Scorecard Added

OSSF Scorecard: 5.6/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 122 spots (#691 → #569)

2026-08-29

HVTrust Changed

HVTrust up 7.9pts (44.3 → 52.2)

2026-08-28

Rank Moved

Rank dropped 25 spots (#666 → #691)

2026-08-27

Rank Moved

Rank dropped 16 spots (#650 → #666)

2026-08-26

Rank Moved

Rank dropped 100 spots (#550 → #650)

2026-08-24

Rank Moved

Rank dropped 15 spots (#535 → #550)

2026-08-23

Rank Moved

Rank rose 16 spots (#551 → #535)

2026-08-23

Activity Score Changed

Activity score up 6pts (54 → 59)

2026-08-22

Rank Moved

Rank rose 11 spots (#562 → #551)

2026-08-20

Rank Moved

Rank rose 15 spots (#579 → #564)

2026-08-13

Rank Moved

Rank dropped 12 spots (#561 → #573)

2026-08-10

Rank Moved

Rank dropped 21 spots (#547 → #568)

2026-08-08

Newly Listed

First tracked at rank #547

GitHub → npm: @verygoodplugins/mcp-automem

Embed Badge Badge guide for maintainers →

For maintainers

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