MCP server · trust report

io.github.nanoodlecom/nanoodle-mcp

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

Publisher
io.github.nanoodlecom
Repository
github.com/nanoodlecom/nanoodle-mcp
Install
npm:nanoodle-mcp, npm:nanoodle-mcp, npm:nanoodle-mcp
Versions
3
MCP revision
2025-06-18 · superseded
Inspected
6 of 6 checks · 100%
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 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 "deslop" description: text addressed to the model rather than describing a capability.

  • Supply chain

    pass25% of grade

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

    repository linkage verified

  • 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. bin/nanoodle-mcp.mjs) — 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/wallet.mjs: 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.3.0 (minor bump): new tool "combine-images" touches a sensitive surface (email/exec/net/fs); new tool "deslop" touches a sensitive surface (email/exec/net/fs); new tool "edit-a-photo" touches a sensitive surface (email/exec/net/fs); new tool "favicon" touches a sensitive surface (email/exec/net/fs); new tool "image-model-arena" touches a sensitive surface (email/exec/net/fs); new tool "photo-to-video" touches a sensitive surface (email/exec/net/fs); new tool "render-a-mockup" touches a sensitive surface (email/exec/net/fs); new tool "sing" touches a sensitive surface (email/exec/net/fs); new tool "talking-avatar" touches a sensitive surface (email/exec/net/fs); new tool "text-to-image" touches a sensitive surface (email/exec/net/fs); new capability primitive(s) in source: http-client; new hardcoded outbound host/BCC destination(s): github.com, nanoodle.com, rpc.nano.to.

  • 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.6.0 · current2026-08-13 D556/6 · 100%B→D in v0.6.0
v0.3.02026-07-19 B1003/6 · 55%±0
v0.1.02026-07-17 B1003/6 · 55%