io.github.antohins/seo-tools-mcp-aparser

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

  tool "aparser_set_credentials" param "APARSER_URL" description: off-vendor URL in a description (ip); 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

  fail15% of grade

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

  tool "aparser_set_credentials" has a secret-shaped input parameter "APARSER_PASSWORD" — secrets must never be tool parameters (the model would supply/handle the credential).

• 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

  warn10% of grade

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

  vs prior 1.7.0 (minor bump): new tool "aparser_auth_status" appeared; new tool "aparser_set_credentials" appeared; new tool "aparser_ping" appeared; new tool "aparser_status" appeared; new tool "aparser_proxies" appeared; new tool "aparser_parsers" appeared; new tool "aparser_parser_fields" appeared; new tool "aparser_get_preset" touches a sensitive surface (email/exec/net/fs); new tool "aparser_serp_google" touches a sensitive surface (email/exec/net/fs); new tool "aparser_serp_yandex" touches a sensitive surface (email/exec/net/fs); new tool "aparser_suggest" appeared; new tool "aparser_request" appeared; new tool "aparser_bulk_request" touches a sensitive surface (email/exec/net/fs).

• Transport config

  unscannable10% of grade

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

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.