updated 2026-09-08 15:33 UTC

Memory Bank MCP

alioshr/memory-bank-mcp

A Model Context Protocol (MCP) server implementation for remote memory bank management, inspired by Cline Memory Bank.

MCP Servers TypeScript Grade D Needs review MIT
30.7/100
Rank #1268 of 1328
Compare Memory Bank MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Needs review
Evidence coverage
Grade B · 3/5 signals
Last push
2025-08-20 · 384d ago
Recent change
Rank +7

Is Memory Bank MCP safe? Memory Bank MCP scores 30.7/100 (Grade D), ranked #1268 of 1328 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 2.0/10; 30% of recent commits are signed; last pushed 2025-08-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Active listing, but review is needed
  • [4.2.1] no meaningful activity in 12 months (last push 2025-08-20)

Ranked neighbours in MCP Servers

#756 Logoloom — 31.1 (D) → #757 Smart Thinking — 31.0 (D) → #759 PapersFlow — 30.6 (D) → #760 MCP Skills Server — 30.6 (D) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-08
Rank Moved
Rank dropped 12 spots (#1256 → #1268)
2026-09-07
Rank Moved
Rank dropped 11 spots (#1245 → #1256)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1230 → #1245)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.0/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.
Refresh maintenance signals The repo was last pushed 384 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[4.2.1] no meaningful activity in 12 months (last push 2025-08-20)
Compare with another agent Get email alerts for Memory Bank MCP View MCP Servers Report missing data
26.8
Activity sub-score · out of 100
#758
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 D 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 →

Signals refreshed 2026-09-08 15:33 UTC · Repo last pushed 384 days ago — may be stale

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
920
Forks
86
Last Push
2025-08-20
384 days ago
Commits (4 wk)
0
Downloads (7d)
134
npm
HN mentions (30d)
—
Open Issues
13
Rank Change
▼12
was #1256

Analysis

HVTrust Dimensions vs MCP Servers

30.7 / 100 · 100.0% confidence

Memory Bank MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.0 / 25
5.9 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
10.2 / 17
1.8 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
10.0 / 20
3.1 above avg 6.9

Activity Inputs

26.8 / 100
StarsRepository reach
17.8 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.0 / 10
OpenSSF Scorecard · scanned Sep 6, 2026
Signed Commits
30%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 2
Contributors 3
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging -1
Pinned-Dependencies 5
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 0

Is Memory Bank MCP safe?

Public trust evidence for Memory Bank MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Memory Bank MCP publish package provenance?
No published build provenance is currently detected for Memory Bank MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Memory Bank MCP have an OpenSSF Scorecard?
Memory Bank MCP has an OpenSSF Scorecard score of 2.0/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 Memory Bank MCP actively maintained?
Stale. The repository has not been pushed to in 384 days. Consider whether the project is still being maintained.
What license does Memory Bank MCP use?
Memory Bank MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Memory Bank MCP's commits signed?
29% of the last 100 commits to Memory Bank 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
Memory Bank 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
high confidence
1 tags
Broad capability areas detected.
  • filesystem
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 Memory Bank 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-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none

Maintain Memory Bank MCP?

For maintainers

HVTrust scores Memory Bank 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
Rank 16HVTrust 2Listed 1Surface 1Warning Issued 1Scorecard 1
2026-09-08
Rank Moved
Rank dropped 12 spots (#1256 → #1268)
2026-09-07
Rank Moved
Rank dropped 11 spots (#1245 → #1256)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1230 → #1245)
2026-09-05
Rank Moved
Rank dropped 20 spots (#1210 → #1230)
2026-09-04
Rank Moved
Rank dropped 18 spots (#1192 → #1210)
2026-09-03
Rank Moved
Rank dropped 43 spots (#1149 → #1192)
2026-09-02
Rank Moved
Rank dropped 39 spots (#1110 → #1149)
2026-09-01
Rank Moved
Rank dropped 42 spots (#1068 → #1110)
2026-08-31
Rank Moved
Rank dropped 29 spots (#1039 → #1068)
2026-08-30
Rank Moved
Rank dropped 56 spots (#983 → #1039)
2026-08-29
Scorecard Added
OSSF Scorecard: 2.0/10
2026-08-29
Rank Moved
Rank rose 283 spots (#1266 → #983)
2026-08-29
HVTrust Changed
HVTrust up 14.6pts (16.4 → 31.0)
2026-08-27
Rank Moved
Rank rose 14 spots (#1273 → #1259)
2026-08-26
Rank Moved
Rank dropped 46 spots (#1227 → #1273)
2026-08-21
Rank Moved
Rank dropped 406 spots (#824 → #1230)
2026-08-21
HVTrust Changed
HVTrust down 10.0pts (26.3 → 16.3)
2026-08-20
Warning Issued
Warning: eligibility issues detected
2026-08-16
Rank Moved
Rank dropped 16 spots (#807 → #823)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-08-12
Rank Moved
Rank rose 17 spots (#815 → #798)
2026-08-10
Newly Listed
First tracked at rank #815
GitHub → npm: @allpepper/memory-bank-mcp

Embed Badge Badge guide for maintainers →

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