io.github.furkan708/mcpify

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

  fail25% of grade

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

  Python build script executes at build time: subprocess in build script

• Credential hygiene

  warn15% of grade

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

  mcpify/http_transport.py: assigns a literal to token (__mc…__ (len 17)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. mcpify/audit.py) — the recommended intake shape.

• Permission scope

  pass15% of grade

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

  Network egress present (mcpify/http_client.py: outbound HTTP/socket call) — expected for most servers and not a finding on its own. No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

• 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.14.0 (minor bump): new capability primitive(s) in source: fs-write, http-client, net, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, a.example.com, api.example.com, api.example.test, api.test, api.weather.gov, api.x.com, auth.example.com, cdn, default.example, dev.example.com, discovered.example, elsewhere, eu.example.com, example.com, flag.example, host, idp, idp.example, one.example.com, override.example, placeholder, prod.example, prod.example.com, staging.example.com, two.example.com, upstream.invalid, x, x.io, x.test.

• 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