updated 2026-10-18 00:07 UTC

Memorylens MCP

Repository by MarcelRoozekrans

MCP server for .NET memory profiling with AI-actionable code fix suggestions, powered by JetBrains dotMemory

MCP Servers C# Listed MIT

Is Memorylens MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.3 / 10
Provenance Attested
Signed commits 100%
Last push yesterday
Advisories None known
Compare Memorylens MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Memorylens MCP scores 79.2/100 (Grade B), ranked #183 of 1378 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 5.3/10; 100% of recent commits are signed; no published advisory affects its latest release (memorylens-mcp); last pushed 2026-10-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How Memorylens 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 Memorylens 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 Signed

    github.com/MarcelRoozekrans/memorylens-mcp, MIT, last pushed 2026-10-17. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection8
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 8
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked and attested

    • npm memorylens-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: memorylens-mcp 2.1.2. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-03 OSSF Scorecard: 5.3/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 Memorylens 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 Memorylens MCP compares in MCP Servers

  1. #94 Openzim MCP 79.2 ±0
  2. #95 Better Notion MCP 79.2 ±0
  3. #96 Memorylens MCP 79.2 this agent
  4. #97 Better Email MCP 79.0 −0.2
  5. #98 Illustrator MCP Server 79.0 −0.2

Bars show each HVTrust score; the tick marks Memorylens MCP’s 79.2.

Where the 79.2 comes from

HVTrust dimensions vs the MCP Servers average

79.2 / 100 · 100.0% confidence

Memorylens MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.1 / 25
8.5 above avg 10.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.4 above avg 13.6
Transparency50% declared license · 50% OSSF Scorecard
13.0 / 17
0.7 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
18.5 / 20
6.3 above avg 12.2
AdoptionLog-scaled stars · package downloads
4.9 / 20
2.5 below avg 7.4

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-10-14
Rank Moved
Rank dropped 18 spots (#165 → #183)
2026-10-06
Grade Changed
Trust grade A → B
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.3/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent Get email alerts for Memorylens MCP View MCP Servers Report missing data
54.8
Activity sub-score · out of 100
#96
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 →

Signals refreshed 2026-10-18 00:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
11
Forks
3
Last Push
2026-10-17
yesterday
Commits (4 wk)
43
Downloads (7d)
55
npm
HN mentions (30d)
—
Open Issues
2
Rank Change
▼1
was #182

Analysis

Activity Inputs

54.8 / 100
StarsRepository reach
6.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
20.5 / 25
CommunityFork signal
2.8 / 20

Common questions about Memorylens MCP

Public supply-chain signals for Memorylens MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Memorylens MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Memorylens MCP publish package provenance?
Yes. Memorylens MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Memorylens MCP have an OpenSSF Scorecard?
Memorylens MCP has an OpenSSF Scorecard score of 5.3/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 Memorylens MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Memorylens MCP use?
Memorylens MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Memorylens MCP's commits signed?
100% of the last 100 commits to Memorylens 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
Memorylens MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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 Memorylens 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
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Memorylens MCP?

For maintainers

HVTrust scores Memorylens 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 20Grade 3Listed 2HVTrust 2Scorecard 1Delisted 1Provenance 1MCP 1Surface 1Surface 1
2026-10-14
Rank Moved
Rank dropped 18 spots (#165 → #183)
2026-10-06
Grade Changed
Trust grade A → B
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 641 spots (#778 → #137)
2026-09-23
HVTrust Changed
HVTrust up 50.9pts (29.3 → 80.2)
2026-09-22
Newly Listed
First tracked at rank #778
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Rank Moved
Rank rose 11 spots (#139 → #128)
2026-09-07
Rank Moved
Rank dropped 12 spots (#115 → #127)
2026-09-05
Rank Moved
Rank dropped 26 spots (#88 → #114)
2026-09-03
Scorecard Added
OSSF Scorecard: 5.3/10
2026-09-03
Grade Changed
Trust grade D → A
2026-09-03
Rank Moved
Rank rose 739 spots (#825 → #86)
2026-09-03
HVTrust Changed
HVTrust up 35.3pts (45.8 → 81.1)
2026-09-02
Rank Moved
Rank dropped 44 spots (#781 → #825)
2026-09-01
Rank Moved
Rank dropped 29 spots (#752 → #781)
2026-08-31
Rank Moved
Rank dropped 34 spots (#718 → #752)
2026-08-30
Rank Moved
Rank dropped 23 spots (#695 → #718)
2026-08-29
Rank Moved
Rank dropped 42 spots (#653 → #695)
2026-08-28
Rank Moved
Rank dropped 20 spots (#633 → #653)
2026-08-27
Rank Moved
Rank dropped 19 spots (#614 → #633)
2026-08-26
Rank Moved
Rank dropped 94 spots (#520 → #614)
2026-08-22
Rank Moved
Rank rose 14 spots (#527 → #513)
2026-08-19
Rank Moved
Rank dropped 10 spots (#517 → #527)
2026-08-17
Rank Moved
Rank rose 11 spots (#527 → #516)
2026-08-13
Rank Moved
Rank dropped 10 spots (#511 → #521)
2026-08-12
Rank Moved
Rank rose 12 spots (#523 → #511)
2026-08-10
Rank Moved
Rank dropped 19 spots (#507 → #526)
2026-08-08
Newly Listed
First tracked at rank #508
GitHub → npm: memorylens-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 79.2 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/memorylens-mcp.svg)](https://hvtracker.net/agents/memorylens-mcp)
HTML:
<a href="https://hvtracker.net/agents/memorylens-mcp"><img src="https://hvtracker.net/badge/memorylens-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