xyz.tereno/tereno

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 93 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

  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. bin/tereno-mcp.mjs) — the recommended intake shape. 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.

  Network egress present (bin/tereno-mcp.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

  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.1.1 (patch bump): tool "tereno_catalog" description changed (wording only, no injection pattern); tool "contract_guard" description changed (wording only, no injection pattern); tool "contract_change" description changed (wording only, no injection pattern); tool "contract_interface" description changed (wording only, no injection pattern); tool "token_metadata" description changed (wording only, no injection pattern); tool "chain_snapshot" description changed (wording only, no injection pattern); tool "evidence_artifact" description changed (wording only, no injection pattern); tool "web_compile" description changed (wording only, no injection pattern); tool "transaction_intent_guard" description changed (wording only, no injection pattern); new tool "tereno_evidence_reference" appeared; new tool "tereno_publish" touches a sensitive surface (email/exec/net/fs); new tool "tereno_find_claims" touches a sensitive surface (email/exec/net/fs); new tool "obligation_verdict" appeared; new capability primitive(s) in source: http-client; new hardcoded outbound host/BCC destination(s): github.com, www.tereno.xyz.

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