io.github.Mrshahidali420/gsc-indexer-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

  unscannable25% of grade

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

  No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.

• Supply chain

  pass25% of grade

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

  Python build script has no build-time network/exec; repository linkage verified

• Credential hygiene

  warn15% of grade

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

  tests/test_logcheck.py: assigns a literal to SECRET (cana…ue (len 19)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. scripts/publish_client.py) — the recommended intake shape.

• Permission scope

  warn15% of grade

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

  has both shell/exec and network egress — capable of download-and-run, though no such path was observed (src/gsc_core/bridge.py: subprocess.* call; src/gsc_core/api.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (src/gsc_core/bridge.py: subprocess.* call; src/gsc_core/gauth.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: src/gsc_core/bridge.py: subprocess.* call discloses shell/exec capability: src/gsc_core/gauth.py: subprocess.* call discloses shell/exec capability: src/gsc_core/pairing.py: subprocess.* call discloses broad/destructive filesystem access: src/gsc_core/gauth.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: src/gsc_core/pairing.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

• 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.0a6 (other bump): new capability primitive(s) in source: http-client, subprocess; new hardcoded outbound host/BCC destination(s): 10.0.0.5, 127.0.0.1, 169.254.169.254, 192.168.1.1, a.b.example.org, a.shop.example.com, accounts.google.com, b.example.org, blog.example.com, cart.shop.example.com, cdn.example.invalid, deep.example.com, elsewhere.invalid, elsewhere.test, example.com, example.net, example.org, github.com, nomatch.example.org, not-yours.example.net, notexample.com, oauth2.googleapis.com, objects.githubusercontent.com, other.example, search.google.com, searchconsole.googleapis.com, shop.eu.example.com, shop.example.com, sub.example.com, typo.example.net, user, www.example.com, www.example.net, www.example.org, www.google.com, www.googleapis.com, www.shahidali.co, www.sitemaps.org.

• Transport config

  warn10% of grade

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

  manifest/source references analytics behavior — disclosure