MCP server · trust report

dev.aicommander/mcp

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

Publisher
dev.aicommander
Repository
github.com/lksrz/aicommander
Install
npm:@aicommander/mcp, npm:@aicommander/mcp, npm:@aicommander/mcp, npm:@aicommander/mcp, npm:@aicommander/mcp, npm:@aicommander/mcp, npm:@aicommander/mcp, npm:@aicommander/mcp, npm:@aicommander/mcp
Versions
9
Inspected
6 of 6 checks · 100%
Scored
2026-09-10 · 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 "remote_exec" description: names an outbound copy/exfil destination (BCC/exfil verb). tool "remote_job_start" description: names an outbound copy/exfil destination (BCC/exfil verb). tool "remote_push" description: off-vendor URL in a description (aicommander.dev); 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 "@aicommander/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate)

  • 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 1.3.0 (patch bump): new tool "remote_exec" whose description contains ignore-previous-instructions phrase; new tool "session_status" touches a sensitive surface (email/exec/net/fs); new tool "list_machines" touches a sensitive surface (email/exec/net/fs); new tool "remote_screenshot" touches a sensitive surface (email/exec/net/fs); new tool "remote_job_start" whose description contains ignore-previous-instructions phrase; new tool "remote_job_list" touches a sensitive surface (email/exec/net/fs); new tool "remote_job_status" touches a sensitive surface (email/exec/net/fs); new tool "remote_job_logs" touches a sensitive surface (email/exec/net/fs); new tool "remote_job_cancel" touches a sensitive surface (email/exec/net/fs); new tool "remote_pull" touches a sensitive surface (email/exec/net/fs); new tool "remote_push" whose description contains embedded outbound URL.

  • Transport config

    pass10% of grade

    Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

    remote endpoint "https://aicommander.dev/mcp" uses TLS (https); remote endpoint uses OAuth (strongest auth mode)

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.3.2 · current2026-09-05 D52.56/6 · 100%B→D in v1.3.2
v1.3.02026-09-04 B87.55/6 · 75%±0
v1.2.12026-09-03 B87.55/6 · 75%±0
v1.1.02026-09-01 B87.55/6 · 75%±0
v1.0.172026-06-27 B87.54/6 · 65%±0
v1.0.152026-06-15 B87.54/6 · 65%—