infinihash-kyt-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KYT_API_KEY | Yes | Your API key for Infinihash KYT. Get one at https://kyt.infinihash.com/kyt/settings/api-keys |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kyt_screen_walletA | Screen a single wallet address against OFAC SDN, stablecoin freezes, ScamSniffer threat intel, and 18.8K+ community-reviewed labels. Returns a 0-100 risk score, matched signals, exposure breakdown, an AI-generated investigation summary, and a recommended action (clear / review / block). Use this BEFORE settling on-chain — sanctioned wallets are caught in <200ms from the fast-path cache. Chain is auto-detected from the address format. |
| kyt_lookup_intelA | Look up known intelligence labels for an address without running a full screen. Returns tiered labels (T1 OFAC SDN, T2 threat intel, T3 on-chain freezes, T4 community-reviewed) with source attribution. Cheaper than a full screen — use when you only need to know whether an address is known. |
| kyt_recent_screeningsA | List recent screenings performed by your organisation. Useful for catching up on what teammates or automated pipelines have been screening. Returns address, chain, score, risk level, and timestamp per row. |
| kyt_create_caseA | Open a compliance case from a flagged screening. A case bundles evidence, notes, and the audit trail you'll need if you escalate to a SAR. Pass the address that triggered the alert; the case is opened under your org with status='open' and tied to the most recent screening of that address. |
| kyt_list_casesA | List your organisation's compliance cases. Filter by status to find cases needing review or escalation. Each case includes id, address, chain, risk level, status, stage, and timestamps. |
| kyt_get_caseA | Fetch a single case by ID, including evidence notes and screening linkage. |
| kyt_add_case_noteA | Append an investigation note to a case. Notes are timestamped, attributed, and form part of the audit trail you'd hand to a regulator. Use this to document transaction hashes, counterparty findings, or analyst rationale. |
| kyt_generate_sarA | Generate a FinCEN-aligned Suspicious Activity Report draft for a case. Returns the SAR as plain text ready for review and submission via the BSA E-Filing System. Compliance Officer remains responsible for review + filing — this is decision-support, not auto-filing. |
| kyt_statsA | Return KYT coverage stats: total labeled addresses (~29K+), per-tier breakdown (T1 OFAC, T2 threat intel, T3 on-chain freezes, T4 community), data sources, and update cadence. Useful for compliance documentation. |
| kyt_healthA | Backend health probe. Returns 'ok' when the KYT screening engine is responsive. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct operation: screening, intel lookup, case management, reporting, and health checks. The screen vs lookup distinction is explicitly explained, and the case-related tools have clear separate responsibilities.
All tools share the kyt_ prefix and most use a verb_noun pattern like create_case and generate_sar. A few noun-only names (stats, health, recent_screenings) cause minor inconsistency, but the overall pattern remains predictable.
Ten tools is well-scoped for a KYT/compliance workflow covering screening, history, statistics, case management, and SAR generation. No redundant tools dilute the set.
Screening and intelligence lookup are well covered, and case creation/listing/fetching exists. However, the case lifecycle is incomplete: there is no update_case tool for status/stage transitions, which is a notable gap in a compliance workflow.