updated 2026-11-10 04:07 UTC

A Mem MCP

Repository
MCP Servers Python Listed MIT

Is A Mem MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.5 / 10
Provenance None
Signed commits 20%
Last push 297d ago
Advisories None known
Compare A Mem MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: A Mem MCP scores 32.0/100 (Grade D), ranked #1317 of 1374 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 1.5/10; 20% of recent commits are signed; no published advisory affects its latest release (a-mem); last pushed 2026-01-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How A Mem 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships A Mem 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.

  1. Source Partly signed

    github.com/DiaaAj/a-mem-mcp, MIT, last pushed 2026-01-17. 20% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 1.5/10 (scanned Oct 25, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI a-mem Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: a-mem 0.2.6. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-08-26 OSSF Scorecard: 1.5/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 A Mem 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 A Mem MCP compares in MCP Servers

  1. #756 MCP Explorium 33.4 +1.4
  2. #757 OneTool MCP 33.4 +1.4
  3. #758 A Mem MCP 32.0 this agent
  4. #759 IBKR Portfolio Builder 31.6 −0.4
  5. #760 Memory Bank MCP 31.6 −0.4

Bars show each HVTrust score; the tick marks A Mem MCP’s 32.0.

Where the 32.0 comes from

HVTrust dimensions vs the MCP Servers average

32.0 / 100 · 100.0% confidence

A Mem MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.9 / 25
7.9 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
9.8 / 17
2.5 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
6.5 / 20
1.1 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.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.
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 297 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
12.1
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-11-10 04:07 UTC · Repo last pushed 297 days ago — may be stale

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
35
Forks
3
Last Push
2026-01-17
297 days ago
Commits (4 wk)
0
Downloads (7d)
126
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #1317

Analysis

Activity Inputs

12.1 / 100
StarsRepository reach
9.3 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.8 / 20

Common questions about A Mem MCP

Public trust evidence for A Mem 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 A Mem MCP publish package provenance?
No published build provenance is currently detected for A Mem 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 A Mem MCP have an OpenSSF Scorecard?
A Mem MCP has an OpenSSF Scorecard score of 1.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 A Mem MCP actively maintained?
Stale. The repository has not been pushed to in 297 days. Consider whether the project is still being maintained.
What license does A Mem MCP use?
A Mem MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are A Mem MCP's commits signed?
20% of the last 100 commits to A Mem 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
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 A Mem 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-23
Provider Added
Runtime surface grew — new detected provider dependencies: Multi-provider (LiteLLM), OpenAI, OpenRouter
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared

Maintain A Mem MCP?

For maintainers

HVTrust scores A Mem 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 17HVTrust 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1
2026-10-09
Rank Moved
Rank dropped 11 spots (#1292 → #1303)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Multi-provider (LiteLLM), OpenAI, OpenRouter
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Rank Moved
Rank rose 41 spots (#1314 → #1273)
2026-09-23
HVTrust Changed
HVTrust up 20.1pts (11.8 → 31.9)
2026-09-22
Newly Listed
First tracked at rank #1314
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank dropped 10 spots (#1255 → #1265)
2026-09-06
Rank Moved
Rank dropped 18 spots (#1219 → #1237)
2026-09-05
Rank Moved
Rank dropped 20 spots (#1199 → #1219)
2026-09-04
Rank Moved
Rank dropped 16 spots (#1183 → #1199)
2026-09-03
Rank Moved
Rank dropped 43 spots (#1140 → #1183)
2026-09-02
Rank Moved
Rank dropped 47 spots (#1093 → #1140)
2026-09-01
Rank Moved
Rank dropped 41 spots (#1052 → #1093)
2026-08-31
Rank Moved
Rank dropped 30 spots (#1022 → #1052)
2026-08-30
Rank Moved
Rank dropped 54 spots (#968 → #1022)
2026-08-29
Rank Moved
Rank dropped 49 spots (#919 → #968)
2026-08-28
Rank Moved
Rank dropped 35 spots (#884 → #919)
2026-08-27
Rank Moved
Rank dropped 28 spots (#856 → #884)
2026-08-26
Scorecard Added
OSSF Scorecard: 1.5/10
2026-08-26
Rank Moved
Rank rose 228 spots (#1084 → #856)
2026-08-26
HVTrust Changed
HVTrust up 12.2pts (20.0 → 32.2)
2026-08-17
Rank Moved
Rank rose 11 spots (#1085 → #1074)
2026-08-16
Rank Moved
Rank dropped 30 spots (#1055 → #1085)
GitHub → PyPI: a-mem

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 32.0 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/a-mem-mcp.svg)](https://hvtracker.net/agents/a-mem-mcp)
HTML:
<a href="https://hvtracker.net/agents/a-mem-mcp"><img src="https://hvtracker.net/badge/a-mem-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON