Satoshkin Aml Mcp

io.github.satoshkin-devPublished by GitHub account satoshkin-devv0.2.0Updated Oct 24, 2026

AML/KYT crypto wallet risk screening (BitOK data) for Claude, ChatGPT and any MCP client.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an assistant screen crypto wallet addresses for AML/KYT risk using Satoshkin's BitOK-backed checks.

What you can do
Check a crypto wallet address for AML/KYT risk on BTC, ETH, TRON, USDT-ERC20 or USDT-TRC20, with client-side address validation before any quota is spent. Return risk score (0-100), risk level, source-of-funds tags, first and last activity dates, and USD volume in and out. Report per-key rate limit and billing details, and return structured error codes such as unauthorized, insufficient_balance or rate_limited. Run in a clearly labeled mock mode with placeholder responses when no API key is set.
When to use it
Useful when an assistant needs quick wallet risk indicators during crypto compliance, OTC settlement, fund vetting or investigation workflows, or when you want to try the screening flow without a key in mock mode.
Requirements
Runs locally via npx from the GitHub repository (Node.js); the package is not yet published to npm. Real checks need a Satoshkin API key in SATOSHKIN_API_KEY (sk_live_ or sk_test_), issued by Satoshkin support. Optional SATOSHKIN_API_BASE_URL and SATOSHKIN_TIMEOUT_MS. Network access to the Satoshkin backend.
Before you install
Real checks are billed per successful check at $0.55, debited from a prepaid key balance (first check per key free; cached repeats within 60 seconds not charged), so usage spends money. The API key is a secret passed via SATOSHKIN_API_KEY. Wallet addresses are sent to the Satoshkin backend and BitOK data. Results are informational risk indicators, not legal or compliance advice.

Installation

In SourceWeft

  1. Open Satoshkin Aml Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Satoshkin AML/KYT MCP Server

[CI] [License: MIT] [MCP] [TypeScript] [Status: v0.2]

MCP server for AML/KYT crypto wallet screening. It is designed to connect AI clients such as Claude Desktop, Claude Code, ChatGPT MCP clients, and internal agent tools to Satoshkin wallet risk checks.

This MCP server provides AI assistants with crypto compliance tools for AML (Anti-Money Laundering) and KYT (Know Your Transaction) screening. Compatible with Claude Desktop, Claude Code, and any MCP-compatible client.

With an API key configured, checks return real BitOK-backed data: risk score 0-100, risk level, source-of-funds tags, activity dates, and volume totals. Without a key the server runs in clearly-labeled mock mode.

Status

v0.2.0 performs real AML/KYT screening through the Satoshkin backend (POST /api-accounts/aml-check, BitOK data) when SATOSHKIN_API_KEY is set.

Without an API key the server runs in mock mode: deterministic, clearly-labeled placeholder responses that can never be mistaken for a real verdict.

This repository does not contain BitOK credentials, production AML/KYT business logic, user data, or paid-tier enforcement. Those belong in the private backend service.

Available Tool

check_wallet_aml

Checks a crypto wallet address for AML/KYT risk. Addresses are validated against per-chain formats client-side before any quota is spent.

Input:

json
{  "address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",  "chain": "BTC"}

Supported chain values:

  • BTC
  • ETH
  • TRON
  • USDT-ERC20
  • USDT-TRC20

Real output (with SATOSHKIN_API_KEY):

json
{  "address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",  "chain": "BTC",  "checked_at": "2026-06-10T12:00:00.000Z",  "risk_score": 17,  "risk_level": "low",  "tags": ["exchange"],  "first_activity": "2021-01-01",  "last_activity": "2026-06-01",  "total_volume_in_usd": "1000.00",  "total_volume_out_usd": "900.00",  "source": "bitok",  "cache_hit": false,  "rate_limit": { "remaining": 999, "resets_at": "2026-06-10T13:00:00.000Z" },  "balance": { "charged_usd": "0.55", "after_usd": "9.45" }}

Errors come back as structured isError payloads with machine-readable codes: unauthorized, insufficient_balance, rate_limited, validation_error, bitok_upstream_error, bitok_timeout, upstream_unreachable, invalid_response, internal_error, and http_<status> (fallback when a backend error body has no error field). Every error payload also carries an http_status field.

Results are informational risk indicators, not legal or compliance advice.

Configuration

Env varDefaultPurpose
SATOSHKIN_API_KEY(unset = mock mode)API key sk_live_* / sk_test_* issued by Satoshkin
SATOSHKIN_API_BASE_URLhttps://satoshkin.comBackend base URL (staging override)
SATOSHKIN_TIMEOUT_MS30000Request timeout; first-time checks may take several seconds

Claude Desktop / Claude Code

This package is not published to npm yet. Use the public GitHub repository through npx.

Add this to your MCP settings:

json
{  "mcpServers": {    "satoshkin-aml": {      "command": "npx",      "args": ["-y", "github:satoshkin-dev/satoshkin-aml-mcp"],      "env": {        "SATOSHKIN_API_KEY": "sk_live_your_key_here"      }    }  }}

Omit the env block to run in mock mode.

For local development, use the built entrypoint:

json
{  "mcpServers": {    "satoshkin-aml": {      "command": "node",      "args": ["/absolute/path/to/satoshkin-aml-mcp/dist/index.js"]    }  }}

Local Development

bash
git clone https://github.com/satoshkin-dev/satoshkin-aml-mcp.gitcd satoshkin-aml-mcpnpm installnpm run buildnpm test

Run the server locally:

bash
npm run dev

Run the built server:

bash
npm run buildnode dist/index.js

Check Scope

Shipped in v0.2:

  • Risk score 0-100 + risk level (low / medium / high)
  • Source-of-funds tags
  • First and last activity dates
  • Total volume in and out (USD)
  • Per-key rate limiting and billing through Satoshkin backend authentication

Planned next: counterparty and cluster analysis, allow/review/block decisions.

Monetization Model

The MCP server is a free open-source connector.

Real checks require a Satoshkin API key. Billing is per successful check ($0.55, debited from a prepaid key balance), the first real check per key is free, and cached repeat checks within 60 seconds are not charged. Keys are currently issued by Satoshkin support; a self-service dashboard is in development. Mock mode is free and unlimited.

Related Satoshkin Products

Use Cases

  • OTC desks: Screen counterparty wallets before settling P2P trades
  • Compliance officers: Quick wallet risk checks during AI-assisted workflows
  • Crypto fund managers: Vet wallet addresses for sanctions/mixer exposure via AI agent
  • Web3 builders: Add AML screening to Claude/ChatGPT-powered dApps
  • Crypto journalists: Investigate wallet history with AI assistance

Why MCP Instead of REST API?

Traditional AML APIs (Chainalysis, Elliptic, TRM Labs) require:

  • Custom integrations per AI client
  • Backend infrastructure to broker calls
  • Manual prompt engineering for context

This MCP server lets any AI assistant call AML checks natively, with structured input/output that the LLM understands. Install once, use across all your AI tools.

Roadmap

  • v0.1: Scaffold with mock checks
  • v0.2: Real BitOK integration via Satoshkin backend (per-check billing, free first check, mock mode without key)
  • v0.3: Self-service key dashboard + top-up
  • v0.4: Additional chains (Solana, BNB, Polygon)
  • v0.5: Richer tag taxonomy and sanctions-specific flags
  • v0.6: Cluster analysis and entity attribution

License

MIT

Source: README.md at commit aab6b5e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts