MCP server · trust report

io.github.BASHBOP/otito

1 check that ran failed — version behavior — so this release can’t be trusted as-is.

Publisher
io.github.BASHBOP
Repository
github.com/BASHBOP/otito
Install
npm:@bashbop/otito, npm:@bashbop/otito, npm:@bashbop/otito, npm:@bashbop/otito, npm:@bashbop/otito, npm:@bashbop/otito, npm:@bashbop/otito, npm:@bashbop/otito, npm:@bashbop/otito, npm:@bashbop/otito, npm:@bashbop/otito
Versions
11
Inspected
5 of 6 checks · 75%
Scored
2026-09-02 · 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 clean4 flagged1 not inspected
  • Injection surface

    unscannable25% of grade

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

    No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.

  • Supply chain

    warn25% of grade

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

    install hook "postinstall" present and not a recognized benign build command

  • 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/lib/catalog.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

    warn15% of grade

    Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

    references credential paths: src/lib/risk-paths.js: references a credential path (id_rsa) has both shell/exec and destructive filesystem writes (src/lib/converge.js: imports child_process and calls exec/spawn; src/lib/catalog.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename)). discloses shell/exec capability: 4 files (src/lib/converge.js, src/lib/init.js, src/lib/tools.js, +1 more) discloses dynamic code execution: src/cli.js: uses eval(…) discloses broad/destructive filesystem access: 11 files (src/lib/catalog.js, src/lib/config.js, src/lib/eval.js, +8 more) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

  • 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.6.1 (minor bump): new capability primitive(s) in source: child_process, dynamic-eval, fs-write, http-client; new hardcoded outbound host/BCC destination(s): bashbop.github.io, cli.github.com, github.com, no-color.org.

  • 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 telemetry 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.7.0 · current2026-08-17 C655/6 · 75%B→C in v1.7.0
v1.6.12026-08-12 B87.53/6 · 55%±0
v1.6.02026-08-02 B755/6 · 75%±0
v1.2.12026-07-30 B754/6 · 65%