MCP server · trust report

io.github.coret/openarchieven-mcp-server

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

Publisher
io.github.coret
Repository
github.com/coret/openarchieven-mcp-server
Install
npm:@coret/openarchieven-mcp-server
Versions
2
MCP revision
2025-11-25 · superseded
Inspected
6 of 6 checks · 100%
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 checks2 clean4 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 138 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.

    dependency "yaml" is edit-distance 2 from popular package "yarn" (typosquat candidate)

  • Credential hygiene

    pass15% of grade

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

    Reads secrets from the environment (e.g. server.ts) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

  • Permission scope

    warn15% of grade

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

    discloses broad/destructive filesystem access: generate.ts: 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

    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.0 (minor bump): new tool "search_records" appeared; new tool "show_record" touches a sensitive surface (email/exec/net/fs); new tool "match_record" appeared; new tool "get_births_years_ago" touches a sensitive surface (email/exec/net/fs); new tool "get_births" appeared; new tool "get_deaths" appeared; new tool "get_marriages" appeared; new tool "get_archives" touches a sensitive surface (email/exec/net/fs); new tool "get_record_stats" appeared; new tool "get_source_type_stats" appeared; new tool "get_event_type_stats" appeared; new tool "get_comment_stats" appeared; new tool "get_family_name_stats" appeared; new tool "get_first_name_stats" appeared; new tool "get_profession_stats" appeared; new tool "get_breakdown" appeared; new tool "get_historical_weather" appeared; new tool "get_census_data" appeared; new tool "search_transcriptions" appeared; new tool "browse_transcriptions" appeared; new tool "show_transcription" appeared; new tool "view_transcription" appeared; new capability primitive(s) in source: fs-write; new hardcoded outbound host/BCC destination(s): api.openarchieven.nl, app.example.org, example.com.

  • 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 heartbeat 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
v1.1.1 · current2026-07-31 C606/6 · 100%B→C in v1.1.1
v1.0.02026-04-25 B87.53/6 · 55%