# io.blockchainanalysis/mcp

Compliance MCP for AI agents: sanctions & KYT screening on 50+ chains, stablecoin-freeze, oracle.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.2.0
- **Author:** io.blockchainanalysis
- **License:** Unknown
- **Endpoints:** streamable-http https://blockchainanalysis.io/api/mcp
- **Source:** https://blockchainanalysis.io/tools/mcp
- **Endpoint health:** reachable (last checked 2026-09-08T05:15:43.144Z, 3 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-08T05:15:43.144Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

11 declared. Observed from a live `tools/list` probe.
- `check_stablecoin_freeze` — Check whether Tether (USDT) or Circle (USDC) have blacklisted a wallet address on-chain. Reads the issuer's blacklist function directly across 15 chains (ETH, B
- `get_freeze_events` — Query the canonical stablecoin freeze ledger — the HISTORY of freeze / unfreeze / destroy events by Tether (USDT), Circle (USDC/EURC), Paxos (USDP) and First Di
- `check_token_security` — Simulate a buy-and-sell of an ERC-20 token on its main DEXes to surface honeypots (tokens you can buy but not sell), extreme transfer taxes, name/symbol imperso
- `check_token_approvals` — List a wallet's active ERC-20 token approvals on Ethereum and who can move its funds — risk-scored against BA's 1B+ entity labels (scam / phishing / exploit / s
- `screen_agent_wallet` — Boolean compliance verdict for an agent wallet or counterparty: clear / flagged / unknown, plus the top risk category, screened against BA's 1B+ entity labels (
- `list_supported_chains` — List the BlockchainAnalysis MCP tools, the chains each supports, and pricing. Call this first to discover what the server can do (and which calls are free vs pa
- `screen_address` — Screen a wallet against BlockchainAnalysis's 1B+ entity-label dataset: sanctions (OFAC / EU / UN / UK HMT / Swiss SECO), scam, phishing, exploit, mixer, exchang
- `kyt_risk` — Assess a wallet's KYT (Know-Your-Transaction) risk: sanctions + entity classification + VASP/jurisdiction score + cluster context → one risk verdict (critical /
- `kyt_tx` — Transaction KYT: screens BOTH counterparties of a transfer (from → to) against sanctions + entity + VASP + cluster, returning a combined risk level, a block/rev
- `oracle_verdict` — Consumer-protection verdict for a wallet or contract: a normalized verdict (safe / caution / high_risk) with a 0-100 score, confidence tier, and plain-language 
- `screen_agent_wallet_attested` — Screen an agent wallet and return a SIGNED, on-chain-anchored compliance attestation: the verdict (clear / flagged / unknown) plus an EIP-712 (secp256k1) signat

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"type\": \"http\",\n      \"url\": \"https://blockchainanalysis.io/api/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.blockchainanalysis%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.blockchainanalysis%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.blockchainanalysis%2Fmcp
- HTML page: https://forgeregistry.com/registry/io.blockchainanalysis%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.