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/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: 14 files (src/hosts/browser.ts, src/commands.ts, src/hosts/github.ts, +11 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 0.2.0 (patch bump): new capability primitive(s) in source: child_process, http-client, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, a, addons.mozilla.org, agent-plugins.org, agents.md, agentskills.io, api.nuget.org, appstoreconnect.apple.com, central.sonatype.com, chrome.google.com, claude.com, clawhub.ai, community.chocolatey.org, containers.dev, copr.fedorainfracloud.org, crates.io, cursor.com, developers.openai.com, docs.astral.sh, docs.github.com, docs.renovatebot.com, example.com, ghcr.io, github.com, go.dev, go.microsoft.com, hermes-agent.nousresearch.com, img.shields.io, json-schema.org, json.schemastore.org, kiro.dev, launchpad.net, marketplace.visualstudio.com, open-vsx.org, packagist.org, partner.microsoft.com, push.chocolatey.org, pypi.org, raw.githubusercontent.com, registry.modelcontextprotocol.io, registry.npmjs.org, rubygems.org, search.maven.org, static.modelcontextprotocol.io, ui.shadcn.com, vite.dev, vscode.dev, www.npmjs.com, www.nuget.org, wxt.dev, x-access-token.

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