io.github.obcraft/apiosk-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).

  tool "apiosk_approval_status" description: instruction to hide activity from the user. server instructions: off-vendor URL in a description (buy.apiosk.com.); capability text should not name where data goes. server instructions: off-vendor URL in a description (gateway.apiosk.com); 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 "@apiosk/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate); dependency "viem" is edit-distance 2 from top-20 package "vue" (typosquat candidate)

• Credential hygiene

  fail15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  tool "apiosk_execute" has a secret-shaped input parameter "offer_token" — secrets must never be tool parameters (the model would supply/handle the credential). Reads secrets from the environment (e.g. src/oauth.mjs) — the recommended intake shape.

• Permission scope

  pass15% of grade

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

  Network egress present (src/external-fetch.mjs: outbound HTTP/socket call) — expected for most servers and not a finding on its own. 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

  unscannable10% of grade

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

  no prior version to diff (first sight of io.github.obcraft/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

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