com.contrastcyber/api

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

  warn25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  tool "robots_txt" description: off-vendor URL in a description (contrastcyber.com); capability text should not name where data goes. tool "redirect_chain" param "url" description: off-vendor URL in a description (bit.ly); capability text should not name where data goes. tool "redirect_chain" param "url" description: off-vendor URL in a description (example.com); capability text should not name where data goes. tool "redirect_chain" param "url" description: off-vendor URL in a description (.); capability text should not name where data goes. tool "ioc_lookup" param "indicator" description: off-vendor URL in a description (evil.com); capability text should not name where data goes. tool "phishing_check" param "url" description: off-vendor URL in a description (suspicious-login.com); capability text should not name where data goes. tool "phishing_check" param "url" description: off-vendor URL in a description (evil.com); capability text should not name where data goes.

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

  No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  unscannable15% of grade

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

  No source files, package.json, or pyproject were fetched; cannot infer capability scope.

• Version behavior

  pass10% of grade

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

  tool surface, capabilities, install scripts, and publisher unchanged vs prior version 1.36.0 (patch bump); no rug-pull drift.

• Transport config

  pass10% of grade

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

  remote endpoint "https://api.contrastcyber.com/mcp/" uses TLS (https); remote endpoint uses OAuth (strongest auth mode)