MCP server · trust report

com.kyrodata/kyrodata

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

Publisher
com.kyrodata
Repository
—
Install
remote only
Versions
10
MCP revision
2025-11-25 · superseded
Inspected
5 of 6 checks · 85%
Scored
2026-09-11 · 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 clean3 flagged1 not inspected
  • Injection surface

    fail25% of grade

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

    tool "kyrodata_run_report" param "reportId" description: names an outbound copy/exfil destination (BCC/exfil verb).

  • 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.0.10 (patch bump): new tool "kyrodata_compare_trade" appeared; new tool "kyrodata_explain_pyramid_level" appeared; new tool "kyrodata_fetch" touches a sensitive surface (email/exec/net/fs); new tool "kyrodata_get_climate_reading" appeared; new tool "kyrodata_get_credit_balance" touches a sensitive surface (email/exec/net/fs); new tool "kyrodata_get_data_coverage" appeared; new tool "kyrodata_get_heading_overview" touches a sensitive surface (email/exec/net/fs); new tool "kyrodata_get_hub_summary" appeared; new tool "kyrodata_get_supply_demand_balance" appeared; new tool "kyrodata_list_trade_partners" appeared; new tool "kyrodata_list_trade_series" appeared; new tool "kyrodata_resolve_comparison_window" appeared; new tool "kyrodata_resolve_entity" touches a sensitive surface (email/exec/net/fs); new tool "kyrodata_run_report" touches a sensitive surface (email/exec/net/fs); new tool "kyrodata_search" touches a sensitive surface (email/exec/net/fs).

  • 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.kyrodata.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.0.13 · current2026-09-11 D52.55/6 · 85%insf→D in v1.0.13
v1.0.102026-09-10 insufficient—3/6 · 45%±0
v1.0.92026-09-08 insufficient—3/6 · 45%±0
v1.0.82026-09-07 insufficient—3/6 · 45%±0
v1.0.72026-09-07 insufficient—3/6 · 45%±0
v1.0.22026-09-06 insufficient—2/6 · 35%C→insf in v1.0.2
v1.0.122026-09-10 C62.54/6 · 75%—