updated 2026-10-16 16:07 UTC

Memory Journal MCP

Repository Website by neverinfamous

Secure AI Memory with Dynamic Project Detection, Automatic Session Briefing, Personal+Team Session Summary Prompts, Triple Search, Knowledge Graphs, GitHub Integration (Issues, PRs, Actions, Kanban, Milestones), Team Collaboration, Hush, Adaptive Analytics, Markdown I/O, Audit+Token Logging, OAuth…

MCP Servers TypeScript Listed MIT

Is Memory Journal MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 5.4 / 10
Provenance None
Signed commits 70%
Last push 86d ago
Compare Memory Journal MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Memory Journal MCP scores 50.0/100 (Grade C), ranked #1009 of 1378 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 5.4/10; 70% of recent commits are signed; last pushed 2026-07-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How Memory Journal 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 Memory Journal MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/neverinfamous/memory-journal-mcp, MIT, last pushed 2026-07-22. 70% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

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

  3. Published packages None

    Distributed as the container image docker.io/writenotenow/memory-journal-mcp:v1.1.3; HVTracker doesn't check that registry's source link yet.

Changes to this chain

  • 2026-09-01 OSSF Scorecard: 6.2/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 Memory Journal 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 Memory Journal MCP compares in MCP Servers

  1. #566 Debridge MCP 50.1 +0.1
  2. #567 Weather MCP Server 50.1 +0.1
  3. #568 Memory Journal MCP 50.0 this agent
  4. #569 Codealive MCP 50.0 ±0
  5. #570 MCP Fns Check 50.0 ±0

Bars show each HVTrust score; the tick marks Memory Journal MCP’s 50.0.

Where the 50.0 comes from

HVTrust dimensions vs the MCP Servers average

50.0 / 100 · 100.0% confidence

Memory Journal MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.2 / 25
in line with avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.1 / 17
0.8 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
6.3 / 20
6.0 below avg 12.3
AdoptionLog-scaled stars · package downloads
8.9 / 20
1.5 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-14
Rank Moved
Rank dropped 14 spots (#986 → #1000)
2026-10-09
Rank Moved
Rank dropped 17 spots (#946 → #963)
2026-09-30
Rank Moved
Rank dropped 17 spots (#910 → #927)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.4/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.
Refresh maintenance signals The repo was last pushed 86 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Memory Journal MCP View MCP Servers Report missing data
25.2
Activity sub-score · out of 100
#568
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 C 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-10-16 16:07 UTC · Repo last pushed 86 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
20
Forks
7
Last Push
2026-07-22
86 days ago
Commits (4 wk)
0
Downloads (7d)
21,440
docker
HN mentions (30d)
—
Open Issues
3
Rank Change
▼3
was #1006

Analysis

Activity Inputs

25.2 / 100
StarsRepository reach
7.9 / 30
FreshnessLast push recency
13.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.2 / 20

Common questions about Memory Journal MCP

Public trust evidence for Memory Journal 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 Journal MCP publish package provenance?
No published build provenance is currently detected for Memory Journal 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 Journal MCP have an OpenSSF Scorecard?
Memory Journal MCP has an OpenSSF Scorecard score of 5.4/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 Journal MCP actively maintained?
Slowing down. Last push was 86 days ago — keep an eye on whether activity resumes.
What license does Memory Journal MCP use?
Memory Journal MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Memory Journal MCP's commits signed?
70% of the last 100 commits to Memory Journal 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 Journal MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • code
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
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 Journal 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
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Memory Journal MCP?

For maintainers

HVTrust scores Memory Journal 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 29HVTrust 7Listed 2Scorecard 1Delisted 1MCP 1Grade 1
2026-10-14
Rank Moved
Rank dropped 14 spots (#986 → #1000)
2026-10-09
Rank Moved
Rank dropped 17 spots (#946 → #963)
2026-09-30
Rank Moved
Rank dropped 17 spots (#910 → #927)
2026-09-25
Grade Changed
Trust grade D → C
2026-09-25
Rank Moved
Rank rose 134 spots (#1038 → #904)
2026-09-25
HVTrust Changed
HVTrust up 5.7pts (45.7 → 51.4)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 64 spots (#1098 → #1034)
2026-09-23
HVTrust Changed
HVTrust up 23.6pts (22.2 → 45.8)
2026-09-22
Newly Listed
First tracked at rank #1098
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 252 spots (#1274 → #1022)
2026-09-19
HVTrust Changed
HVTrust up 14.0pts (32.1 → 46.1)
2026-09-18
Rank Moved
Rank dropped 289 spots (#985 → #1274)
2026-09-18
HVTrust Changed
HVTrust down 15.8pts (47.9 → 32.1)
2026-09-16
Rank Moved
Rank rose 10 spots (#987 → #977)
2026-09-15
Rank Moved
Rank dropped 10 spots (#977 → #987)
2026-09-12
Rank Moved
Rank dropped 13 spots (#964 → #977)
2026-09-11
Rank Moved
Rank dropped 12 spots (#952 → #964)
2026-09-09
Rank Moved
Rank dropped 13 spots (#941 → #954)
2026-09-08
Rank Moved
Rank dropped 17 spots (#924 → #941)
2026-09-07
Rank Moved
Rank rose 308 spots (#1232 → #924)
2026-09-07
HVTrust Changed
HVTrust up 16.0pts (32.6 → 48.6)
2026-09-06
Rank Moved
Rank dropped 360 spots (#872 → #1232)
2026-09-06
HVTrust Changed
HVTrust down 16.1pts (48.7 → 32.6)
2026-09-05
Rank Moved
Rank dropped 57 spots (#815 → #872)
2026-09-04
Rank Moved
Rank dropped 30 spots (#785 → #815)
2026-09-03
Rank Moved
Rank dropped 48 spots (#737 → #785)
2026-09-02
Rank Moved
Rank dropped 38 spots (#699 → #737)
2026-09-01
Scorecard Added
OSSF Scorecard: 6.2/10
2026-09-01
Rank Moved
Rank rose 563 spots (#1262 → #699)
2026-09-01
HVTrust Changed
HVTrust up 30.6pts (18.4 → 49.0)
2026-08-31
Rank Moved
Rank dropped 11 spots (#1251 → #1262)
2026-08-30
Rank Moved
Rank dropped 16 spots (#1235 → #1251)
2026-08-29
Rank Moved
Rank dropped 14 spots (#1221 → #1235)
2026-08-28
Rank Moved
Rank dropped 13 spots (#1208 → #1221)
2026-08-27
Rank Moved
Rank dropped 12 spots (#1196 → #1208)
2026-08-26
Rank Moved
Rank dropped 43 spots (#1153 → #1196)
2026-08-19
Rank Moved
Rank dropped 10 spots (#1133 → #1143)
2026-08-16
Rank Moved
Rank dropped 29 spots (#1114 → #1143)
2026-08-10
Rank Moved
Rank dropped 69 spots (#1046 → #1115)
2026-08-08
Newly Listed
First tracked at rank #1044
GitHub → Website →

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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