IAPI MCP Server

A Model Context Protocol (MCP) server for the Chainalysis Investigations API (IAPI), hosted on Cloudflare Workers.

Overview

This MCP server provides access to 16 key Chainalysis IAPI endpoints through standardized MCP tools for cryptocurrency investigation and analysis.

Available Tools

Address Info

• getTransactionHashesByAddress - Get transaction hashes for an address

Cluster Info

• getClusterInfo - Get cluster name and category for an address

• getClusterAddresses - Get addresses in a cluster

• getClusterSummary - Get cluster balance and summary stats

• getClusterTransactions - Get transactions for a cluster

• getClusterCounterparties - Get counterparties for a cluster

Transaction Info

• getTransactionInfo - Get transaction time and asset info

• getTransactionDetails - Get detailed transaction information

Exposure Info

• getExposureByCategory - Get directed exposure by category

• getExposureByService - Get directed exposure by service

Wallet Observations

• getObservationsByIP - Get observations for IP address

• getObservationsByCountry - Get observations by country

• getObservationsByCity - Get observations by city

• getObservationsForCluster - Get observations for cluster

Usage Info

• getUsageByOrg - Get API usage by organization

• getUsageByUser - Get API usage by user

Setup

1. Install dependencies:

   npm install

2. Set up your Chainalysis API key:

   wrangler secret put CHAINALYSIS_API_KEY

3. Deploy to Cloudflare Workers:

   npm run deploy

Development

Run locally:

Lint code:

Type check:

API Usage

The server responds to POST requests with MCP protocol messages. Each tool requires specific parameters as defined in the tool schemas.

Example request:

Authentication

The server requires a valid Chainalysis API key set as the CHAINALYSIS_API_KEY environment variable/secret.

Supported Assets

The server supports all assets available in the Chainalysis IAPI, including:

• Bitcoin (BTC)

• Ethereum (ETH) and ERC-20 tokens

• Bitcoin Cash (BCH)

• Litecoin (LTC)

• And many others as listed in the IAPI documentation

Error Handling

The server provides standard MCP error responses for:

• Invalid requests

• Authentication failures

• IAPI rate limits

• Missing parameters

• Network issues