MCP server · trust report

ai.shumi/mcp

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

Publisher
ai.shumi
Repository
github.com/shumi-ai/shumi-mcp
Install
npm:@shumi-ai/mcp, npm:@shumi-ai/mcp, npm:@shumi-ai/mcp, npm:@shumi-ai/mcp, npm:@shumi-ai/mcp, npm:@shumi-ai/mcp
Versions
7
MCP revision
2025-11-25 · superseded
Inspected
6 of 6 checks · 100%
Scored
2026-09-04 · 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 checks2 clean4 flagged
  • Injection surface

    pass25% of grade

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

    Scanned 237 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.

  • Supply chain

    warn25% of grade

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

    package name "@shumi-ai/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate); dependency "@modelcontextprotocol/node" is edit-distance 2 from popular package "@babel/core" (typosquat candidate); dependency "@modelcontextprotocol/server" is edit-distance 1 from popular package "semver" (typosquat candidate)

  • Credential hygiene

    fail15% of grade

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

    tool "get_pair_suggestions" has a secret-shaped input parameter "token_a" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_pair_suggestions" has a secret-shaped input parameter "token_b" — 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

    fail10% of grade

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

    vs prior 1.1.0 (patch bump): new hardcoded outbound host/BCC destination(s): github.com, shumi.ai.

  • 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); sends telemetry to third-party SDK (posthog) — disclosure, verify opt-in

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.1.1 · current2026-08-26 D52.56/6 · 100%C→D in v1.1.1
v1.1.02026-08-19 C62.56/6 · 100%±0
v0.1.32026-08-12 C62.55/6 · 90%