store.scvd/general-store

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

  pass25% of grade

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

  Scanned 155 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.

• Supply chain

  warn25% of grade

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

  dependency "@x402/core" is edit-distance 1 from popular package "cors" (typosquat candidate); dependency "@x402/evm" is edit-distance 2 from popular package "ejs" (typosquat candidate); dependency "@x402/hono" is edit-distance 2 from popular package "pino" (typosquat candidate); dependency "@x402/svm" is edit-distance 2 from popular package "@anthropic-ai/sdk" (typosquat candidate); dependency "hono" is edit-distance 2 from popular package "pino" (typosquat candidate); dependency "viem" is edit-distance 2 from top-20 package "vue" (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.2.2 (patch bump): tool "preflight_endpoint" description changed (wording only, no injection pattern); tool "check_before_you_pay" description changed (wording only, no injection pattern); tool "check_conformance" description changed (wording only, no injection pattern); tool "buy_simple" description changed (wording only, no injection pattern); tool "buy_signed_record" description changed (wording only, no injection pattern); tool "buy_human_task" description changed (wording only, no injection pattern); tool "buy_human_task" gained input property(ies): url; tool "buy_observation" description changed (wording only, no injection pattern); tool "buy_observation" gained input property(ies): mandate_id, claim, launch_check_id, address; tool "buy_small_pleasure" description changed (wording only, no injection pattern); new tool "look_at_door" touches a sensitive surface (email/exec/net/fs); new hardcoded outbound host/BCC destination(s): github.com, scvd.store.

• Transport config

  fail10% of grade

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

  remote MCP endpoint declares NO authentication (unauthenticated remote — nginx-ui/CVE-2026-33032 class)