MCP server · trust report

io.github.livevariant/livevariant

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

Publisher
io.github.livevariant
Repository
github.com/livevariant/livevariant
Install
npm:@livevariant/mcp, npm:@livevariant/mcp, npm:@livevariant/mcp, npm:@livevariant/mcp
Versions
4
MCP revision
2025-11-25 · superseded
Inspected
6 of 6 checks · 100%
Scored
2026-08-31 · 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 clean5 flagged
  • Injection surface

    warn25% of grade

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

    server instructions: off-vendor URL in a description (livevariant.com); capability text should not name where data goes.

  • Supply chain

    warn25% of grade

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

    package name "@livevariant/mcp" is edit-distance 2 from popular package "yup" (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_stats" has a secret-shaped input parameter "statsSecret" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_test_status" has a secret-shaped input parameter "statsSecret" — secrets must never be tool parameters (the model would supply/handle the credential). tool "register_test" has a secret-shaped input parameter "statsSecret" — 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 0.1.1 (patch bump): tool "inspect_test" gained input property(ies): config; tool "generate_priors" gained input property(ies): config; tool "get_stats" gained input property(ies): config; tool "get_test_status" gained input property(ies): config; new hardcoded outbound host/BCC destination(s): github.com.

  • 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.1.5 · current2026-08-27 D406/6 · 100%±0
v0.1.12026-08-24 D505/6 · 90%