MCP for Crypto Compliance and Wallet Screening

Every crypto withdrawal is a compliance decision made under a clock. Before funds leave your platform, you need to know whether the destination wallet is sanctioned, whether it has touched a mixer, and whether it sits close to counterparties you cannot serve — and you need to know it fast enough not to hurt legitimate users. That is structured, evidence-driven work an AI agent can carry out in seconds when it has a dependable screening tool to call. The Didit Model Context Protocol (MCP) server exposes Wallet Screening — Know Your Transaction (KYT) — as a natural-language tool, so an agent can screen an address, read the exposure, and gate a withdrawal inside a single conversation.

This post covers crypto compliance over MCP: connecting a client, screening a wallet before a withdrawal for sanctions, mixer exposure, and high-risk counterparties, applying the Travel Rule, and running KYT at $0.15 per check.

Key takeaways

• Didit's MCP server exposes Wallet Screening among its 130+ tools across 11 categories, so an AI agent can screen a crypto address and interpret the risk in one exchange.
• Wallet Screening (KYT) checks an address for sanctions, mixer exposure, and high-risk counterparties across fiat and crypto at $0.15 per check.
• Screening runs before a withdrawal, so a risky destination is caught before funds move rather than reconstructed afterward.
• Travel Rule is supported, so the originator and beneficiary information required for qualifying transfers can be handled in the same flow.
• Authentication is OAuth 2.1 with Proof Key for Code Exchange (PKCE) — "Log in with Didit," no Application Programming Interface (API) key for the hosted server, scoped to your console role.
• You get 500 free checks per month and sub-2-second responses; the MCP layer is free, and each wallet screen is $0.15 beyond the free tier.

What wallet screening looks at

Wallet Screening answers a focused question about a blockchain address: how risky is it to send funds here, or to accept funds from here? Didit's KYT module evaluates three things at once. Sanctions exposure asks whether the address itself, or addresses closely linked to it, appear on sanctions watchlists. Mixer exposure asks whether the wallet's funds have passed through services designed to obscure their trail, a classic laundering signal. High-risk counterparty exposure asks whether the wallet transacts with entities you cannot serve — darknet markets, known theft addresses, high-risk exchanges. A single screen at $0.15 returns all three in structured form in under two seconds, and it works across both fiat rails and crypto.

Over MCP, your agent calls that module and receives the same structured exposure payload a direct integration would, then turns it into a clear go/no-go recommendation for the analyst or the automated flow.

Connecting your agent to the MCP server

The server runs at https://mcp.didit.me/mcp over Streamable HTTP — hosted, or self-hosted from the open-source repository under the MIT license. Authentication is OAuth 2.1 with PKCE: on first connect a "Log in with Didit" flow opens, there is no API key to paste for the hosted endpoint, and the agent inherits your console role through the didit:management and didit:verification scopes — it can only do what your account permits.

Add the server to Claude Code in one line, then confirm with /mcp:

claude mcp add --transport http didit https://mcp.didit.me/mcp

Claude Desktop, Cursor, VS Code, Windsurf, and Zed connect via a small JSON configuration pointing at the same URL. ChatGPT Developer Mode can attach through OpenAI's beta MCP support, which is still early, so treat that surface as experimental. The connection matrix is in the MCP overview docs.

Screening a wallet before a withdrawal

The decisive moment in crypto compliance is the instant before funds leave. Screen the destination there, and a bad withdrawal never happens; screen it afterward, and you are chasing money that is already gone. Over MCP, that pre-withdrawal check is a sentence:

"Screen this wallet for sanctions and high-risk exposure: 0x9f8a…c210, before we release the withdrawal."

The agent calls the Wallet Screening tool with the address, waits for the sub-2-second response, and returns a structured read: any sanctions hits, whether there is mixer exposure and how direct it is, and which high-risk counterparties the wallet is connected to. It then recommends an action — release, hold for manual review, or block — with the exposure that drove it. For an incoming deposit, the phrasing is the same:

"Check the source wallet on this incoming deposit for mixer exposure and sanctions before we credit the account."

Because the agent holds the conversation, you can drill in without re-entering context: "How many hops from the mixer?" or "Show me only the sanctions-linked counterparties."

Interpreting exposure and gating the transfer

Not every hit means block, and not every clean screen means release. A wallet two hops removed from a mixer through a major exchange is a different risk than one that received funds directly from a sanctioned address. This interpretation step is where an agent adds value, because it reasons over the structured exposure rather than reacting to a single flag:

"For that wallet, tell me whether the mixer exposure is direct or indirect, how close the sanctioned counterparty is, and whether this clears your withdrawal policy."

The agent lines the exposure up against your thresholds and explains the call: direct sanctions exposure is an automatic block; distant, diluted mixer exposure through a regulated venue may clear with a note. A human owns the final decision on the edge cases; the agent makes the routine ones fast and consistent, and documents why each transfer was gated the way it was — which is what an examiner will ask for later.

Applying the Travel Rule

Qualifying crypto transfers between institutions carry a Travel Rule obligation: the originating platform must pass identifying information about the sender and the recipient to the receiving platform. Didit's Wallet Screening supports the Travel Rule, so the compliance data required for a transfer can be handled in the same flow that screened the wallet. Your agent can prepare it alongside the screen:

"This is a $12,000 transfer to another exchange — screen the wallet and prepare the Travel Rule originator and beneficiary information."

Screening the counterparty and assembling the required transfer information become one continuous step, so a transfer that needs the Travel Rule applied does not get released without it. That keeps qualifying transfers compliant without a separate manual handoff to a different system.

Fitting wallet screening into the broader risk picture

Wallet screening rarely stands alone. A withdrawal you are unsure about often deserves a look at the customer behind it, and a suspicious pattern of transfers belongs in your monitoring queue. Because the same MCP server also exposes Transaction Monitoring and Anti-Money Laundering (AML) Screening, your agent can move between them in one conversation: screen the wallet, then check whether the customer has open monitoring flags, then run an AML screen on the account holder if the picture warrants it. The agent orchestrates across the fraud tools you already have, so a single "is this withdrawal safe to release?" question can pull in every relevant signal instead of forcing three separate console visits.

Start free

Crypto compliance over MCP means your team asks the question — screen this wallet, apply the Travel Rule, gate this withdrawal — and the agent returns the exposure, the reasoning, and a defensible decision in the same exchange, before funds move. Didit is used by 1,500+ companies, is backed by $7.5M in funding, is a Y Combinator W26 company, is profitable, and covers 220+ countries and territories. Start free: 500 checks per month at no cost, the MCP layer free, and $0.15 per wallet screen beyond the free tier. Read the MCP overview, explore the developer hub, or self-host the open-source server and point your agent at your withdrawal flow today.