1 check that ran failed — supply chain — so this release can’t be trusted as-is.
- Publisher
- io.github.n24q02m
- Repository
- github.com/n24q02m/mnemo-mcp.git
- Install
- pypi:mnemo-mcp, oci:docker.io/n24q02m/mnemo-mcp:latest, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp, pypi:mnemo-mcp
- Versions
- 57
- Inspected
- 5 of 6 checks · 75%
- Scored
- 2026-09-03 · rubric 1.0.0
What we checked
Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.
Injection surface
unscannable25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.
Supply chain
fail25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
Python build script executes at build time: network call in build script
Credential hygiene
pass15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
Reads secrets from the environment (e.g. src/mnemo_mcp/capture.py) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.
Permission scope
warn15% of gradeDeclared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.
discloses broad/destructive filesystem access: src/mnemo_mcp/setup_tool.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.
Version behavior
pass10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
tool surface, capabilities, install scripts, and publisher unchanged vs prior version 2.9.0 (minor bump); no rug-pull drift.
Transport config
warn10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
manifest/source references tracking behavior — disclosure
Version history
Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.
| Version | Published | Grade | Score | Inspected | Change |
|---|---|---|---|---|---|
| v2.10.1 · current | 2026-09-02 | C | 62.5 | 5/6 · 75% | B→C in v2.10.1 |
| v2.9.0 | 2026-08-31 | B | 75 | 4/6 · 65% | ±0 |
| v2.8.0 | 2026-08-29 | B | 75 | 4/6 · 65% | ±0 |
| v2.7.0 | 2026-07-18 | B | 75 | 3/6 · 55% | C→B in v2.7.0 |
| v2.1.4 | 2026-06-01 | C | 67.5 | 3/6 · 55% | B→C in v2.1.4 |
| v1.26.0 | 2026-05-06 | B | 75 | 3/6 · 55% | ±0 |
| v1.20.0 | 2026-04-13 | B | 75 | 3/6 · 55% | — |