io.github.jgravelle/jdatamunch-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.

  Python build script has no build-time network/exec; repository linkage verified

• Credential hygiene

  warn15% of grade

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

  tests/test_redact.py: embeds a PRIVATE KEY block. (in an example/sample file — lower severity, but a real key here still leaks.) tests/test_runtime_ingest.py: contains a hardcoded JWT (eyJh…5c (len 92)) — in an example/sample file; verify it is not a real key. Reads secrets from the environment (e.g. benchmarks/harness/run_tier_surface.py) — the recommended intake shape.

• Permission scope

  warn15% of grade

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

  discloses broad/destructive filesystem access: 4 files (src/jdatamunch_mcp/storage/data_store.py, src/jdatamunch_mcp/storage/data_store.py, src/jdatamunch_mcp/tools/index_repo.py, +1 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 1.31.12 (patch bump): new capability primitive(s) in source: fs-write, http-client, subprocess; new hardcoded outbound host/BCC destination(s): ..., a.test, api.github.com, example.com, foo.bar, github.com, j.gravelle.us.

• 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 telemetry behavior — disclosure