MCP server · trust report

io.github.beepboop2025/groundcheck

3 checks that ran failed — injection surface, version behavior and transport config — so this release can’t be trusted as-is.

Publisher
io.github.beepboop2025
Repository
github.com/beepboop2025/groundcheck
Install
npm:groundcheck-mcp, npm:groundcheck-mcp, npm:groundcheck-mcp
Versions
6
MCP revision
2025-11-25 · superseded
Inspected
6 of 6 checks · 100%
Scored
2026-09-01 · 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 checks3 clean3 flagged
  • Injection surface

    fail25% of grade

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

    tool "attest_delivery" description: URL on a cheap/abused TLD (api.vendor.xyz) — postmark-mcp used giftshop.club. server instructions: off-vendor URL in a description (api.seiche.info); capability text should not name where data goes. server instructions: off-vendor URL in a description (api.liquilens.in); 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

    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

    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.7.0 (patch bump): new hardcoded outbound host/BCC destination(s): github.com, groundcheck.seiche.info.

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

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
v0.7.1 · current2026-08-16 D556/6 · 100%C→D in v0.7.1
v0.7.02026-08-02 C655/6 · 90%D→C in v0.7.0
v0.6.12026-07-27 D556/6 · 100%B→D in v0.6.1
v0.6.02026-07-26 B1004/6 · 65%±0
v0.4.02026-07-12 B1003/6 · 55%