MCP server · trust report

io.github.KrystalView/krystalview

2 checks that ran failed — supply chain and version behavior — so this release can’t be trusted as-is.

Publisher
io.github.KrystalView
Repository
github.com/KrystalView/krystalview-mcp
Install
pypi:krystalview-mcp, pypi:krystalview-mcp, pypi:krystalview-mcp, pypi:krystalview-mcp
Versions
4
MCP revision
2025-06-18 · superseded
Inspected
6 of 6 checks · 100%
Scored
2026-09-03 · 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

    pass25% of grade

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

    Scanned 79 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

    fail25% of grade

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

    Python build script executes at build time: network call in build script

  • Credential hygiene

    pass15% of grade

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

    Reads secrets from the environment (e.g. src/krystalview_mcp/server.py) — the recommended intake shape. 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.

    Network egress present (src/krystalview_mcp/server.py: outbound HTTP/socket call) — expected for most servers and not a finding on its own. 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.5 (patch bump): new tool "get_sessions" touches a sensitive surface (email/exec/net/fs); new tool "get_session_detail" appeared; new tool "get_site_stats" appeared; new tool "get_scroll_depth" appeared; new tool "get_live_visitors" appeared; new tool "get_anomalies" appeared; new tool "get_funnels" appeared; new tool "get_funnel_analysis" appeared; new tool "get_campaign_summary" appeared; new tool "get_campaign_sessions" appeared; new tool "get_campaign_roas" appeared; new tool "get_errors" appeared; new tool "get_notifications" appeared; new capability primitive(s) in source: http-client; new hardcoded outbound host/BCC destination(s): app.krystalview.com, docs.krystalview.com, github.com, krystalview.com.

  • 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

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.6 · current2026-06-10 C606/6 · 100%B→C in v0.1.6
v0.1.52026-06-05 B753/6 · 55%