Is State Memory MCP safe to use?

State Memory MCP has an HVTrust score of 65.7/100 (Grade B), ranked #503 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for State Memory MCP?

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

State Memory MCP

Repository

Website

Persistent, branch-aware workflow state memory MCP server for AI coding assistants. Tracks tasks, accepted decisions, and active blockers to prevent session context bloat and speed up development.

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 4.1 / 10

Provenance Attested

Signed commits 9%

Last push 38d ago

Advisories None known

Compare State Memory MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: State Memory MCP scores 65.7/100 (Grade B), ranked #503 of 1374 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 4.1/10; 9% of recent commits are signed; no published advisory affects its latest release (@putervision/state-memory-mcp); last pushed 2026-10-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How State Memory MCP 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.

Raise the OSSF Scorecard from 4.1 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Contributors 0 +10.2 → 75.9 B · #147 of 778
Sign every commit9% signed today +4.5 → 70.2 B · #222 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships State Memory MCP 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/putervision/state-memory-mcp, MIT, last pushed 2026-10-03. 9% 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 4.1/10 (scanned Nov 6, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies2
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 2

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 1
Published packages Linked and attested
- npm @putervision/state-memory-mcp Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: @putervision/state-memory-mcp 1.4.1. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

2026-09-29 Package provenance attestation detected
2026-08-31 OSSF Scorecard: 4.1/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 State Memory MCP’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.

Signed credential (JSON) How to verify

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 State Memory MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks State Memory MCP’s 65.7.

Where the 65.7 comes from

HVTrust dimensions vs the MCP Servers average

65.7 / 100 · 100.0% confidence

State Memory MCP MCP Servers average (778 agents)

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

13.1 / 25

2.3 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

12.0 / 17

in line with avg 12.3

Maintenance60% last-push freshness · 40% commit activity

9.5 / 20

2.7 below avg 12.2

AdoptionLog-scaled stars · package downloads

7.1 / 20

in line with avg 7.6

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-11-07

Rank Moved

Rank rose 13 spots (#515 → #502)

2026-11-05

Rank Moved

Rank dropped 10 spots (#498 → #508)

2026-11-02

Rank Moved

Rank dropped 64 spots (#434 → #498)

Maintainer Checklist

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

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

Refresh maintenance signals The repo was last pushed 38 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent View MCP Servers Report missing data

32.4

Activity sub-score · out of 100

#290

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-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-10-03

38 days ago

Commits (4 wk)

Downloads (7d)

242

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #505

Analysis

Activity Inputs

32.4 / 100

StarsRepository reach

9.7 / 30

FreshnessLast push recency

19.7 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.8 / 20

Common questions about State Memory MCP

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

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

Does State Memory MCP have an OpenSSF Scorecard?

State Memory MCP has an OpenSSF Scorecard score of 4.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 State Memory MCP actively maintained?

Slowing down. Last push was 38 days ago — keep an eye on whether activity resumes.

What license does State Memory MCP use?

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

Are State Memory MCP's commits signed?

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

State Memory MCP appears to expose MCP server capabilities.

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

How this surface has changed

Detected changes to State Memory MCP'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-29

Provenance Added

Package provenance attestation detected

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain State Memory MCP?

For maintainers

HVTrust scores State Memory MCP 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-11-07

Rank Moved

Rank rose 13 spots (#515 → #502)

2026-11-05

Rank Moved

Rank dropped 10 spots (#498 → #508)

2026-11-02

Rank Moved

Rank dropped 64 spots (#434 → #498)

2026-11-02

Activity Score Changed

Activity score down 6pts (40 → 33)

2026-11-01

Rank Moved

Rank dropped 59 spots (#375 → #434)

2026-11-01

Activity Score Changed

Activity score down 7pts (47 → 40)

2026-10-30

Rank Moved

Rank dropped 24 spots (#345 → #369)

2026-10-29

Rank Moved

Rank dropped 12 spots (#333 → #345)

2026-10-26

Rank Moved

Rank dropped 25 spots (#300 → #325)

2026-10-22

Rank Moved

Rank dropped 49 spots (#248 → #297)

2026-10-13

Rank Moved

Rank dropped 12 spots (#231 → #243)

2026-10-09

Rank Moved

Rank dropped 23 spots (#199 → #222)

2026-10-03

Rank Moved

Rank rose 11 spots (#203 → #192)

2026-10-02

Rank Moved

Rank rose 14 spots (#217 → #203)

2026-09-30

Rank Moved

Rank rose 36 spots (#254 → #218)

2026-09-29

Provenance Added

Package provenance attestation detected

2026-09-27

Rank Moved

Rank rose 59 spots (#737 → #678)

2026-09-26

Activity Score Changed

Activity score up 6pts (47 → 53)

2026-09-24

Rank Moved

Rank rose 49 spots (#780 → #731)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 241 spots (#1021 → #780)

2026-09-23

HVTrust Changed

HVTrust up 30.6pts (24.5 → 55.1)

2026-09-22

Newly Listed

First tracked at rank #1021

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank dropped 38 spots (#738 → #776)

2026-09-18

Rank Moved

Rank dropped 12 spots (#726 → #738)

2026-09-16

Rank Moved

Rank rose 14 spots (#744 → #730)

2026-09-15

Rank Moved

Rank rose 16 spots (#760 → #744)

2026-09-12

Rank Moved

Rank dropped 28 spots (#723 → #751)

2026-09-11

Rank Moved

Rank dropped 81 spots (#642 → #723)

2026-09-10

Rank Moved

Rank rose 80 spots (#722 → #642)

2026-09-08

Rank Moved

Rank dropped 12 spots (#703 → #715)

2026-09-07

Rank Moved

Rank dropped 23 spots (#680 → #703)

2026-09-05

Rank Moved

Rank dropped 81 spots (#591 → #672)

2026-09-04

Rank Moved

Rank dropped 52 spots (#539 → #591)

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 479 spots (#1018 → #539)

2026-09-03

HVTrust Changed

HVTrust up 18.6pts (38.1 → 56.7)

2026-09-02

Rank Moved

Rank dropped 45 spots (#973 → #1018)

2026-09-01

Rank Moved

Rank dropped 42 spots (#931 → #973)

2026-08-31

Scorecard Added

OSSF Scorecard: 4.1/10

2026-08-31

Rank Moved

Rank rose 239 spots (#1170 → #931)

2026-08-31

HVTrust Changed

HVTrust up 16.1pts (22.0 → 38.1)

2026-08-30

Rank Moved

Rank dropped 35 spots (#1135 → #1170)

2026-08-29

Rank Moved

Rank dropped 33 spots (#1102 → #1135)

2026-08-28

Rank Moved

Rank dropped 27 spots (#1075 → #1102)

2026-08-27

Rank Moved

Rank dropped 29 spots (#1046 → #1075)

2026-08-26

Rank Moved

Rank dropped 88 spots (#958 → #1046)

2026-08-24

Rank Moved

Rank dropped 18 spots (#940 → #958)

2026-08-22

Rank Moved

Rank rose 11 spots (#954 → #943)

2026-08-20

Rank Moved

Rank rose 17 spots (#971 → #954)

2026-08-17

Rank Moved

Rank rose 12 spots (#971 → #959)

2026-08-16

Rank Moved

Rank dropped 33 spots (#938 → #971)

GitHub → Website → npm: @putervision/state-memory-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

State Memory MCP

How State Memory MCP could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How State Memory MCP compares in MCP Servers

Where the 65.7 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about State Memory MCP

AI agent surface

Maintain State Memory MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers