io.github.tamasPetki/headless-tracker

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. src/mcp/orchestrator.ts) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  warn15% of grade

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

  discloses broad/destructive filesystem access: src/mcp/tools/account_admin.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/connectors/binance.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/connectors/bybit.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/mcp/tools/get_holdings.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/mcp/tools/get_pnl.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/connectors/hyperliquid.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/connectors/metamask.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/connectors/polymarket.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/mcp/tools/refresh_data.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/mcp/apps/dashboard/register.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/mcp/apps/settings/register.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/observability/sentry.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/mcp/server.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/mcp/tools/setup_connector.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/connectors/solana.ts: path traversal ('../') combined with file access discloses broad/destructive filesystem access: src/connectors/types.ts: path traversal ('../') combined with file access 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.0.16 (patch bump): new hardcoded outbound host/BCC destination(s): api.hyperliquid.xyz, hyperliquid.gitbook.io.

• 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