Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.stillmarcus24/stillos-kya

NPM · STILLOS-KYA · 2 COMPONENTS · SCANNED AUG 3

KYA: fail-closed CLEAR/REVIEW/BLOCK counterparty screen (OFAC + on-chain), signed receipt.

Available components

remote · stillos-kya-edge.stillos.workers.dev 58 npm · stillos-kya 68
−12 this week 68 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 117 tokens (~117/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · stillos-kya

# add to Claude Code
claude mcp add stillmarcus24-stillos-kya -- npx -y stillos-kya
# add to Codex CLI
codex mcp add stillmarcus24-stillos-kya -- npx -y stillos-kya
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stillmarcus24-stillos-kya": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "stillos-kya"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add stillmarcus24-stillos-kya --command npx --arg -y --arg stillos-kya
# ~/.hermes/config.yaml
mcp_servers:
  stillmarcus24-stillos-kya:
    command: "npx"
    args: ["-y", "stillos-kya"]
// mcp.json
{
  "mcpServers": {
    "stillmarcus24-stillos-kya": {
      "command": "npx",
      "args": [
        "-y",
        "stillos-kya"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +15
    • Malware scan: unverified → pass ▲ security
  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +22
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −51
    • Malware scan: pass → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 0.2.1 → 0.3.1 functional
  • 27 Jul 26 +33
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: good functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: fail functional
  • 26 Jul 26 47

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 0 packages

0 packages in the resolved dependency tree.

MCP tools — 1 exposed · ~117 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
kya_check ~117

Know Your Agent (KYA): screen a counterparty agent BEFORE paying it. Returns a fail-closed verdict — CLEAR, REVIEW, or BLOCK — from an OFAC SDN sanctions screen plus live on-chain wallet signals, with an Ed25519-signed proof-of-diligence receipt on the paid tier. Call this before any agent-to-agent payment.

NameTypeReqDescription
namestring—Counterparty legal/display name to sanctions-screen (optional)
walletstring—Counterparty EVM wallet address for on-chain risk signals (optional)

No output schema declared.

No examples provided.