MCP server · trust report

com.ou-reports/just-signal

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

Publisher
com.ou-reports
Repository
Install
npm:just-signal-mcp, npm:just-signal-mcp
Versions
2
Inspected
6 of 6 checks · 100%
Scored
2026-07-21 · 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

    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 (ou-reports.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.

    no resolvable repository linked to the package (provenance unverifiable)

  • 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. index.js) — 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 (index.js: 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 1.0.1 (minor bump): new tool "get_stock_quote" appeared; new tool "publish_report" appeared; new tool "list_reports" appeared; new tool "get_scorecard" appeared; new tool "get_panel_grade" touches a sensitive surface (email/exec/net/fs); new capability primitive(s) in source: http-client; new hardcoded outbound host/BCC destination(s): fonts.googleapis.com, fonts.gstatic.com, ou-reports.com, schema.org, www.ou-reports.com, www.w3.org.

  • 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); manifest/source references TRACKING 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.2.0 · current2026-07-09 D556/6 · 100%B→D in v1.2.0
v1.0.12026-07-06 B87.53/6 · 55%