MCP server · trust report

io.github.Abracadabrastartup/deusproof-mcp

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

Publisher
io.github.Abracadabrastartup
Repository
github.com/Abracadabrastartup/deusproof-mcp
Install
pypi:deusproof-mcp, pypi:deusproof-mcp, pypi:deusproof-mcp, pypi:deusproof-mcp, pypi:deusproof-mcp
Versions
10
MCP revision
2025-11-25 · superseded
Inspected
6 of 6 checks · 100%
Scored
2026-09-01 · 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 clean5 flagged
  • Injection surface

    warn25% of grade

    Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

    tool "council_ballot" description: imperative telling the model it must read/send/attach something.

  • 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. deusproof_mcp/server.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.

    discloses broad/destructive filesystem access: deusproof_mcp/server.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

    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.1.9 (minor bump): new tool "legacy_testament" appeared; new capability primitive(s) in source: http-client; new hardcoded outbound host/BCC destination(s): deusproof.com.

  • Transport config

    fail10% of grade

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

    remote MCP endpoint declares NO authentication (unauthenticated remote — nginx-ui/CVE-2026-33032 class)

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.2.0 · current2026-08-27 F356/6 · 100%D→F in v0.2.0
v0.1.92026-08-11 D47.56/6 · 100%±0
v0.1.82026-08-08 D52.55/6 · 90%C→D in v0.1.8
v0.1.72026-08-05 C606/6 · 100%±0
v0.1.62026-08-04 C606/6 · 100%B→C in v0.1.6
v0.1.42026-07-24 B92.53/6 · 55%±0
v0.1.32026-07-13 B92.54/6 · 65%±0
v0.1.22026-07-13 B92.53/6 · 55%