MCP server · trust report

io.github.seunghan91/ainote

3 checks that ran failed — credential hygiene, permission scope and transport config — so this release can’t be trusted as-is.

Publisher
io.github.seunghan91
Repository
github.com/seunghan91/ainote
Install
npm:@ainote/mcp, npm:@ainote/mcp
Versions
2
Inspected
5 of 6 checks · 90%
Scored
2026-07-20 · 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

    pass25% of grade

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

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

    warn25% of grade

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

    package name "@ainote/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate); dependency "open" is edit-distance 2 from popular package "boxen" (typosquat candidate)

  • Credential hygiene

    fail15% of grade

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

    tool "signup_and_get_key" has a secret-shaped input parameter "password" — secrets must never be tool parameters (the model would supply/handle the credential). tool "login_and_get_key" has a secret-shaped input parameter "password" — secrets must never be tool parameters (the model would supply/handle the credential). tool "env_sync.device_enroll" has a secret-shaped input parameter "enrollment_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "env_sync.device_request_secret_share" has a secret-shaped input parameter "secret_shares" — secrets must never be tool parameters (the model would supply/handle the credential). Reads secrets from the environment (e.g. lib/core/config-manager.js) — the recommended intake shape.

  • Permission scope

    fail15% of grade

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

    HIGH: shell/exec capability AND network egress together — download-and-execute risk (lib/tools/dev-doc-tools.js: imports child_process and calls exec/spawn; package.json depends on HTTP client "axios"). HIGH: shell/exec capability AND destructive filesystem writes together (lib/tools/dev-doc-tools.js: imports child_process and calls exec/spawn; lib/utils/api-client.js: path traversal ('../') combined with file access). discloses shell/exec capability: lib/tools/dev-doc-tools.js: imports child_process and calls exec/spawn discloses shell/exec capability: lib/tools/internal/encryption.js: imports child_process and calls exec/spawn discloses shell/exec capability: lib/tools/internal/path-mapper.js: imports child_process and calls exec/spawn discloses broad/destructive filesystem access: lib/utils/api-client.js: path traversal ('../') combined with file access discloses broad/destructive filesystem access: lib/tools/internal/claude-scanner.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename) discloses broad/destructive filesystem access: lib/core/config-manager.js: path traversal ('../') combined with file access discloses broad/destructive filesystem access: lib/tools/dev-doc-tools.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename) discloses broad/destructive filesystem access: lib/tools/dev-doc-tools.js: path traversal ('../') combined with file access discloses broad/destructive filesystem access: lib/tools/internal/encryption.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename) discloses broad/destructive filesystem access: lib/tools/internal/keychain.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename) discloses broad/destructive filesystem access: lib/cli/login.js: path traversal ('../') combined with file access discloses broad/destructive filesystem access: lib/auth/mcp-key.js: path traversal ('../') combined with file access discloses broad/destructive filesystem access: lib/tools/onboarding-tools.js: path traversal ('../') combined with file access discloses broad/destructive filesystem access: lib/tools/internal/path-mapper.js: path traversal ('../') combined with file access discloses broad/destructive filesystem access: lib/cli/signup.js: path traversal ('../') combined with file access discloses broad/destructive filesystem access: lib/auth/token-store.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

  • Version behavior

    unscannable10% of grade

    Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

    no prior version to diff (first sight of io.github.seunghan91/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

  • 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
v1.3.2 · current2026-05-14 D47.55/6 · 90%