MCP server · trust report

io.github.cyanheads/ris-austria-mcp-server

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

Publisher
io.github.cyanheads
Repository
github.com/cyanheads/ris-austria-mcp-server
Install
npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server, npm:@cyanheads/ris-austria-mcp-server
Versions
15
MCP revision
2025-11-25 · superseded
Inspected
6 of 6 checks · 100%
Scored
2026-09-01 · 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

    warn25% of grade

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

    tool "ris_get_document" param "document_url" description: off-vendor URL in a description (www.ris.bka.gv.at); capability text should not name where data goes.

  • Supply chain

    pass25% of grade

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

    install hook "prepare" is a recognized benign build command; repository linkage verified

  • 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 0.4.1 (patch bump): tool "ris_track_changes" description changed (wording only, no injection pattern); new hardcoded outbound host/BCC destination(s): caseyjhand.com, data.bka.gv.at, github.com, mcp.example.com, www.buymeacoffee.com, www.ris.bka.gv.at.

  • 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); manifest/source references Telemetry behavior — disclosure

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.4.2 · current2026-08-25 C67.56/6 · 100%B→C in v0.4.2
v0.4.12026-07-31 B77.55/6 · 90%±0
v0.2.52026-07-26 B77.55/6 · 90%±0
v0.2.02026-07-16 B77.55/6 · 90%