MCP server · trust report

io.github.usenotra/notra

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

Publisher
io.github.usenotra
Repository
github.com/usenotra/notra-mcp
Install
remote only
Versions
9
Inspected
5 of 6 checks · 75%
Scored
2026-09-04 · 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 clean2 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.

    package name "@usenotra/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate); dependency "@modelcontextprotocol/node" is edit-distance 2 from popular package "@babel/core" (typosquat candidate); dependency "@modelcontextprotocol/server" is edit-distance 1 from popular package "semver" (typosquat candidate); dependency "@usenotra/geo" is edit-distance 2 from top-20 package "glob" (typosquat candidate); dependency "jose" is edit-distance 2 from popular package "@babel/core" (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.0.8 (minor bump): new hardcoded outbound host/BCC destination(s): github.com, mcp.usenotra.com.

  • 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://mcp.usenotra.com/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.1.0 · current2026-08-31 B77.55/6 · 75%±0
v1.0.82026-07-18 B87.54/6 · 65%±0
v1.0.72026-07-02 B87.54/6 · 65%±0
v1.0.22026-04-07 B87.54/6 · 65%