BlockchainAnalysis
REMOTE · BLOCKCHAINANALYSIS.IO · SCANNED AUG 3
Is a wallet frozen by Tether/Circle? Free freeze checks + full history, screening & KYT. 9 chains.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1553 tokens (~172/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · blockchainanalysis.io
claude mcp add --transport http io-blockchainanalysis-mcp https://blockchainanalysis.io/api/mcp
[mcp_servers.io-blockchainanalysis-mcp] url = "https://blockchainanalysis.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-blockchainanalysis-mcp": {
"type": "remote",
"url": "https://blockchainanalysis.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add io-blockchainanalysis-mcp --url https://blockchainanalysis.io/api/mcp --transport streamable-http
mcp_servers:
io-blockchainanalysis-mcp:
url: "https://blockchainanalysis.io/api/mcp" {
"mcpServers": {
"io-blockchainanalysis-mcp": {
"type": "http",
"url": "https://blockchainanalysis.io/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 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.
- 31 Jul 26 +1
- 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 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 63
First indexed and scored.
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 · Probed https://blockchainanalysis.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=blockchainanalysis.io | CN=YE1,O=Let's Encrypt,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5106428247a82b282c0197aa6e717a9e392 |
| SANs: *.blockchainanalysis.io, blockchainanalysis.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of blockchainanalysis.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| blockchainanalysis.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://cdnjs.cloudflare.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' https://api.stripe.com https://*.neon.tech https://*.sentry.io https://open.er-api.com; frame-src https://js.stripe.com; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://blockchainanalysis.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://blockchainanalysis.io/api/mcp | HTTPS enforced | 301 | https://blockchainanalysis.io/api/mcp |
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.
check_stablecoin_freeze Check stablecoin freeze ~218
Check whether Tether (USDT) or Circle (USDC) have blacklisted a wallet address on-chain. Reads the issuer's blacklist function directly across 9 chains (ETH, BSC, POLYGON, ARBITRUM, OPTIMISM, BASE, AVALANCHE, TRON, SOL). A frozen address can no longer send or receive that stablecoin. Also reports whether the address was PREVIOUSLY frozen and later unfrozen (a prior-freeze signal from the freeze ledger). The result reports the observed on-chain fact (frozen / not frozen at check time), never the cause of a freeze. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address to check. Format must match the chain (0x… for EVM, T… for Tron, base58 for Solana). |
| chain | string | yes | Chain to check. One of: ETH, BSC, POLYGON, ARBITRUM, OPTIMISM, BASE, AVALANCHE, TRON, SOL |
No output schema declared.
No examples provided.
check_token_approvals Check token approvals ~100
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 / sanctioned spenders), flagging unlimited allowances and stale grants. The wallet's attack surface at a glance. Read-only. Ethereum only. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | Wallet address to scan (0x + 40 hex). Ethereum only. |
No output schema declared.
No examples provided.
check_token_security Check token security ~164
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 impersonation, and active mint authority — cross-referenced against BA's 1B+ entity labels. Reports observed facts (e.g. 'sell simulation reverted'), not verdicts. Live on Base, BNB Chain, Ethereum, Optimism, Polygon, Arbitrum. No transaction is sent. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain to scan. One of: BASE, BSC, ETH, OPTIMISM, POLYGON, ARBITRUM |
| token | string | yes | ERC-20 token contract address (0x + 40 hex). |
No output schema declared.
No examples provided.
get_freeze_events Get stablecoin freeze events (history) ~292
Query the canonical stablecoin freeze ledger — the HISTORY of freeze / unfreeze / destroy events by Tether (USDT), Circle (USDC/EURC), Paxos (USDP) and First Digital (FDUSD), sourced from the issuers' own on-chain blacklist events across Ethereum, Polygon, Optimism, TRON and more. Filter by frozen address, chain, kind, or time; omit all filters for the most recent events. This is the EVENT HISTORY — to check whether an address is frozen right now, use check_stablecoin_freeze instead. Each row is a verifiable on-chain fact (issuer acted on address at block/time); it never states the cause. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | — | Filter to a single frozen wallet address (case-insensitive). Omit to list across all addresses. |
| chain | string | — | Filter by chain code, e.g. ETH, POLYGON, OPTIMISM, TRON. Omit for all chains. |
| kind | string | — | Filter by event kind: 'freeze' (blacklisted), 'unfreeze' (removed), 'destroy' (funds burned). |
| limit | integer | — | Max events to return (default 50, hard cap 500). Ordered newest first. |
| since | string | — | Only events at/after this time. ISO 8601 or YYYY-MM-DD (UTC). |
No output schema declared.
No examples provided.
kyt_risk ~172
Assess a wallet's KYT (Know-Your-Transaction) risk: combines real-time sanctions screening, BA entity classification, a VASP/jurisdiction risk score, and cluster context into a single risk verdict (critical / high / medium / low / unknown) with flags. Behavioral risk, distinct from a raw label list. Covers 11 chains: Ethereum, Bitcoin, Tron, Solana, BSC, Polygon, Arbitrum, Optimism, Base, Avalanche, Linea. Paid per call via x402 (USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address to assess (format must match the chain). |
| chain | string | yes | Chain ID, uppercase — e.g. ETH, BTC, TRON, SOL, BSC, POLYGON, ARBITRUM, BASE. |
No output schema declared.
No examples provided.
kyt_tx ~209
Assess the KYT risk of a transaction between two wallets: screens BOTH the sender (from) and recipient (to) against real-time sanctions, BA entity classification, a VASP/jurisdiction risk score and cluster context, then returns a single combined risk verdict (critical / high / medium / low / unknown), a block/review/allow recommendation, and directional flags (FROM:/TO:). The transaction analogue of kyt_risk. Covers 11 chains: Ethereum, Bitcoin, Tron, Solana, BSC, Polygon, Arbitrum, Optimism, Base, Avalanche, Linea. Paid per call via x402 (USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain ID, uppercase — e.g. ETH, BTC, TRON, SOL, BSC, POLYGON, ARBITRUM, BASE. |
| from | string | yes | Sender wallet address (format must match the chain). |
| to | string | yes | Recipient wallet address (format must match the chain). |
No output schema declared.
No examples provided.
list_supported_chains List supported chains & tools ~51
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 paid) before invoking a tool. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
oracle_verdict ~182
Get a consumer-protection verdict for a wallet or contract: a normalized verdict (e.g. safe / caution / high_risk) with a 0-100 score, confidence tier, and plain-language reasons, derived from BA sanctions + entity labels. Answers 'is it safe to interact with this address?' Distinct from raw labels (screen_address) and transactional risk (kyt_risk). Supported chains: btc, eth, bsc, polygon, arbitrum, optimism, base, avalanche, fantom, tron, sol. Paid per call via x402 (USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet or contract address (format must match the chain). |
| chain | string | yes | Chain ID, lowercase — one of: btc, eth, bsc, polygon, arbitrum, optimism, base, avalanche, fantom, tron, sol |
No output schema declared.
No examples provided.
screen_address ~165
Screen a wallet against BlockchainAnalysis's 1B+ entity-label dataset: sanctions (OFAC / EU / UN / UK HMT / Swiss SECO), scam, phishing, exploit, mixer, exchange, and more — each label carries a threat level (SAFE→CRITICAL), source, and confidence. Returns the raw labels for the address. Works across major EVM chains plus TRON, SOL, and BTC. Paid per call via x402 (USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address to screen (format must match the chain). |
| chain | string | yes | Chain ID, uppercase — e.g. ETH, BSC, POLYGON, ARBITRUM, OPTIMISM, BASE, AVALANCHE, TRON, SOL, BTC. |
No output schema declared.
No examples provided.