MCP server · trust report

com.kairossignal/kairos-signal

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

Publisher
com.kairossignal
Repository
Install
remote only
Versions
9
MCP revision
2024-11-05 · superseded
Inspected
5 of 6 checks · 85%
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 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 "register_agent" description: off-vendor URL in a description (kairossignal.com); capability text should not name where data goes. server instructions: off-vendor URL in a description (kairossignal.com); 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

    fail15% of grade

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

    tool "purchase_data" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "topup_credits" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "check_balance" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential).

  • 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 3.6.0 (patch bump): tool "register_agent" description changed and now contains embedded outbound URL; new tool "get_data_dictionary" touches a sensitive surface (email/exec/net/fs); new tool "get_derivation_ledger" 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://kairossignal.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
v3.6.2 · current2026-08-28 D505/6 · 85%F→D in v3.6.2
v3.6.02026-08-25 F37.55/6 · 85%±0
v3.3.02026-08-11 F37.54/6 · 75%±0
v3.4.02026-08-19 F37.54/6 · 75%±0
v3.2.02026-07-31 F37.54/6 · 75%