io.github.sjkim1127/reversecore-mcp

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

  pass25% of grade

  Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

  repository linkage verified

• 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. reversecore_mcp/core/extension_registry.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

  fail15% of grade

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

  HIGH: executes content derived from a network response (reversecore_mcp/tools/malware/rop_builder.py: passes a network response into an exec/eval call). has both shell/exec and destructive filesystem writes (reversecore_mcp/tools/forensics/disk.py: subprocess.* call; reversecore_mcp/server.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: 4 files (reversecore_mcp/tools/forensics/disk.py, reversecore_mcp/tools/forensics/memory.py, reversecore_mcp/tools/malware/poc_generator.py, +1 more) discloses broad/destructive filesystem access: 6 files (reversecore_mcp/server.py, reversecore_mcp/tools/analysis/crash_triage.py, reversecore_mcp/tools/analysis/fuzzing_campaign.py, +3 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 3.0.2 (patch bump): new capability primitive(s) in source: fs-write, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, docs.oasis-open.org, evil.com, 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 tracking behavior — disclosure