updated 2026-08-12 05:02 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 Listed MIT
25.8/100
Rank #814 of 1283
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
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2025-08-20 · 357d ago
Recent change
New

Is Memory Bank MCP safe? Memory Bank MCP scores 25.8/100 (Grade D), ranked #814 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 30% of recent commits are signed; last pushed 2025-08-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#391 Scriptivox MCP Server — 25.9 (D) → #392 MCP Server for Excel — 25.9 (D) → #394 KonQuest Meta Ads MCP — 25.8 (D) → #395 Buildkite MCP Server — 25.8 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Newly Listed
First tracked at rank #815
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 357 days ago. Fresh activity helps separate stable projects from stale ones.
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
#393
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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 357 days ago — may be stale

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
915
Forks
85
Last Push
2025-08-20
357 days ago
Commits (4 wk)
0
Downloads (7d)
202
npm
HN mentions (30d)
—
Open Issues
13
Rank Change
▲1
was #815

Analysis

HVTrust Dimensions vs MCP Servers

25.8 / 100 · 67.0% confidence

Memory Bank MCP MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.5 / 25
3.5 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.4 below avg 12.4
AdoptionLog-scaled stars · package downloads
10.2 / 20
4.4 above avg 5.8

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
—
Not available
Signed Commits
30%
of last 100 commits verified

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?
No OpenSSF Scorecard data is currently published for Memory Bank MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Memory Bank MCP actively maintained?
Stale. The repository has not been pushed to in 357 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
Extensions
Extension based plugin/integration surface 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

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
Listed 1
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 25.8 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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON