MCP server · trust report

org.ungovr/mcp

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

Publisher
org.ungovr
Repository
Install
remote only
Versions
4
MCP revision
2025-03-26 · superseded
Inspected
5 of 6 checks · 85%
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

    warn25% of grade

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

    tool "search_cgj_reports" description: off-vendor URL in a description (www.ungovr.org); capability text should not name where data goes. tool "search_cgj_reports" description: off-vendor URL in a description (data.ungovr.org); capability text should not name where data goes. tool "get_cgj_report" description: off-vendor URL in a description (www.ungovr.org); capability text should not name where data goes. tool "get_scraping_law" description: off-vendor URL in a description (www.ungovr.org); capability text should not name where data goes. tool "resolve_domain_jurisdiction" description: off-vendor URL in a description (www.ungovr.org); capability text should not name where data goes. tool "resolve_domain_jurisdiction" param "domain" description: off-vendor URL in a description (www.stadt-koeln.de); capability text should not name where data goes.

  • Supply chain

    warn25% of grade

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

    no resolvable repository linked to the package (provenance unverifiable)

  • 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

    unscannable15% of grade

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

    No source files, package.json, or pyproject were fetched; cannot infer capability scope.

  • 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.1.0 (minor bump): new tool "get_scraping_law" whose description contains embedded outbound URL; new tool "resolve_domain_jurisdiction" whose description contains embedded outbound URL.

  • 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.2.0 · current2026-08-13 D555/6 · 85%C→D in v1.2.0
v1.1.02026-08-12 C654/6 · 75%