MCP server · trust report

io.github.nulib/dc-api

2 checks that ran failed — supply chain and transport config — so this release can’t be trusted as-is.

Publisher
io.github.nulib
Repository
github.com/nulib/dc-api-v2
Install
npm:@nulib/dc-api-mcp, oci:ghcr.io/nulib/dc-api-mcp:2.10.10, npm:@nulib/dc-api-mcp, oci:ghcr.io/nulib/dc-api-mcp:2.10.3, npm:@nulib/dc-api-mcp, oci:ghcr.io/nulib/dc-api-mcp:2.11.0, npm:@nulib/dc-api-mcp, oci:ghcr.io/nulib/dc-api-mcp:2.11.5, npm:@nulib/dc-api-mcp, oci:ghcr.io/nulib/dc-api-mcp:2.11.6
Versions
5
Inspected
6 of 6 checks · 100%
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 checks4 clean2 flagged
  • 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 65 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

    fail25% of grade

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

    install hook "prepare" contains self-delete/cleanup

  • 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

    pass10% of grade

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

    tool surface, capabilities, install scripts, and publisher unchanged vs prior version 2.11.5 (patch bump); no rug-pull drift.

  • 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
v2.11.6 · current2026-07-20 C656/6 · 100%±0
v2.11.52026-06-12 C655/6 · 90%