net.tasklite/mcp

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

  fail25% of grade

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

  server instructions: instruction to hide activity from the user. tool "create_automation" param "actions" description: off-vendor URL in a description (api.frankfurter.app); capability text should not name where data goes. tool "deploy_frontend" description: off-vendor URL in a description ({slug}.tasklite.dev); capability text should not name where data goes. server instructions: off-vendor URL in a description (tasklite.net); capability text should not name where data goes. server instructions: off-vendor URL in a description ({slug}.tasklite.dev); capability text should not name where data goes.

• Supply chain

  warn25% of grade

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

  package name "@tasklite/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate)

• 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

  pass15% of grade

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

  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 0.13.0 (minor bump): new hardcoded outbound host/BCC destination(s): github.com, tasklite.net.

• 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://mcp.tasklite.net/mcp" uses TLS (https); remote endpoint uses OAuth (strongest auth mode)