MCP server · trust report

io.github.saurabhsharma2u/search-console-mcp

Passes 1 check with a soft flag on supply chain, credential hygiene and transport config — worth a look, not a dealbreaker.

Publisher
io.github.saurabhsharma2u
Repository
github.com/saurabhsharma2u/search-console-mcp
Install
npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp, npm:search-console-mcp
Versions
16
Inspected
4 of 6 checks · 65%
Scored
2026-07-20 · rubric 1.0.0

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.

6 checks1 clean3 flagged2 not inspected
  • 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

    warn25% of grade

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

    dependency "re2" is edit-distance 2 from popular package "pm2" (typosquat candidate); dependency "open" is edit-distance 2 from popular package "boxen" (typosquat candidate)

  • Credential hygiene

    warn15% of grade

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

    .env.example: embeds a PRIVATE KEY block. (in an example/sample file — lower severity, but a real key here still leaks.)

  • 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

    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.saurabhsharma2u/[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

    warn10% of grade

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

    sends telemetry to third-party SDK (google-analytics) — disclosure, verify opt-in; manifest/source references Analytics behavior — disclosure

Version history

Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.

VersionPublishedGradeScoreInspectedChange
v1.14.1 · current2026-07-15 B754/6 · 65%±0
v1.13.52026-04-05 B87.53/6 · 55%