io.github.GoatInAHat/toolfactory

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

  warn25% of grade

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

  dependency "yaml" is edit-distance 2 from popular package "yarn" (typosquat candidate); dependency "@modelcontextprotocol/node" is edit-distance 2 from popular package "@babel/core" (typosquat candidate); dependency "@modelcontextprotocol/client" is edit-distance 2 from popular package "@aws-sdk/client-s3" (typosquat candidate); dependency "@modelcontextprotocol/server" is edit-distance 1 from popular package "semver" (typosquat candidate)

• Credential hygiene

  warn15% of grade

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

  src/surfaces/dsh.test.ts: assigns a literal to APIKEY (proc…EY (len 18)) — non-provider secret literal; prefer environment intake. src/project/gate.ts: assigns a literal to api-key ($FIR…ER (len 19)) — non-provider secret literal; prefer environment intake. src/project/gate.ts: assigns a literal to secret ($FIR…ET (len 19)) — non-provider secret literal; prefer environment intake. src/surfaces/mcpb.test.ts: assigns a literal to APIKEY (${us…y} (len 21)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. src/surfaces/agents.template.ts) — the recommended intake shape.

• Permission scope

  fail15% of grade

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

  HIGH: downloads and pipes straight to a shell (src/surfaces/hermes-native.ts: pipes a download into a shell). references credential paths: src/surfaces/agents.template.ts: references a credential path (/mcp.json) references credential paths: src/surfaces/agents.ts: references a credential path (/mcp.json) references credential paths: src/surfaces/cursor.ts: references a credential path (/mcp.json) discloses shell/exec capability: 12 files (src/hosts/browser.ts, src/commands.ts, src/hosts/github.ts, +9 more) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

• Version behavior

  unscannable10% of grade

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

  no prior version to diff (first sight of io.github.GoatInAHat/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

• Transport config

  unscannable10% of grade

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

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.