io.github.davidgringras/scrutica

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

  resource "methodology-flop-estimation" description: off-vendor URL in a description (scrutica.com); capability text should not name where data goes. resource "methodology-cost-index" description: off-vendor URL in a description (scrutica.com); capability text should not name where data goes. resource "methodology-compute-visibility-index" description: off-vendor URL in a description (scrutica.com); capability text should not name where data goes. resource "methodology-supply-chain-weighting" description: off-vendor URL in a description (scrutica.com); capability text should not name where data goes. resource "methodology-chokepoint-cascade" description: off-vendor URL in a description (scrutica.com); capability text should not name where data goes. resource "methodology-sovereign-execution-classification" description: off-vendor URL in a description (scrutica.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).

  vs prior 0.1.0 (minor bump): tool "scrutica_get_facility" gained input property(ies): entity_id, id; tool "scrutica_get_company" gained input property(ies): org_id, organization_id, entity_id, id; tool "scrutica_query_export_controls" description changed (wording only, no injection pattern); tool "scrutica_get_supply_chain" description changed (wording only, no injection pattern); tool "scrutica_get_supply_chain" gained input property(ies): org_id, company_id; tool "scrutica_get_sovereign_program" description changed (wording only, no injection pattern); tool "scrutica_get_scenario" description changed (wording only, no injection pattern); new tool "scrutica_entity_list_changes" appeared. Low-severity drift (informational; consistent with the version bump).

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