MCP server · trust report

io.github.mnemox-ai/tradememory-protocol

2 checks that ran failed — supply chain and version behavior — so this release can’t be trusted as-is.

Publisher
io.github.mnemox-ai
Repository
github.com/mnemox-ai/tradememory-protocol
Install
pypi:tradememory-protocol, pypi:tradememory-protocol, pypi:tradememory-protocol
Versions
3
Inspected
5 of 6 checks · 75%
Scored
2026-09-09 · 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.

6 checks1 clean4 flagged1 not inspected
  • Injection surface

    unscannable25% of grade

    Tool 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 grade

    Package 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 grade

    How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

    Reads secrets from the environment (e.g. src/tradememory/audit/tsa.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 grade

    Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

    references credential paths: src/tradememory/onboarding/platforms.py: references a credential path (/mcp.json) has both shell/exec and network egress — capable of download-and-run, though no such path was observed (src/tradememory/onboarding/setup_wizard.py: subprocess.* call with shell=True (command-injection prone); src/tradememory/audit/tsa.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (src/tradememory/onboarding/setup_wizard.py: subprocess.* call with shell=True (command-injection prone); src/tradememory/onboarding/setup_wizard.py: open(…, 'w'/'a'/'x') write-mode file access). discloses shell/exec capability: src/tradememory/onboarding/setup_wizard.py: subprocess.* call with shell=True (command-injection prone) discloses broad/destructive filesystem access: 5 files (src/tradememory/onboarding/setup_wizard.py, src/tradememory/replay/engine.py, src/tradememory/simulation/report.py, +2 more) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

  • Version behavior

    fail10% of grade

    Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

    vs prior 0.5.4 (patch bump): new capability primitive(s) in source: fs-write, http-client, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, api.binance.com, api.deepseek.com, console.anthropic.com, example.tsa, fake.tsa, freetsa.org, github.com.

  • Transport config

    warn10% of grade

    Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

    manifest/source references analytics 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.

VersionPublishedGradeScoreInspectedChange
v0.5.5 · current2026-09-08 D52.55/6 · 75%B→D in v0.5.5
v0.5.42026-07-29 B754/6 · 65%±0
v0.3.12026-03-02 B753/6 · 55%—