Compliance MCP server
{
"mcpServers": {
"onchaindiligence-compliance": {
"type": "http",
"url": "https://mcp.onchaindiligence.com/mcp"
}
}
}{
"mcpServers": {
"onchaindiligence-compliance": {
"type": "http",
"url": "https://mcp.onchaindiligence.com/mcp"
}
}
}{
"mcpServers": {
"onchaindiligence-compliance": {
"type": "http",
"url": "https://mcp.onchaindiligence.com/mcp"
}
}
}{
"servers": {
"onchaindiligence-compliance": {
"type": "http",
"url": "https://mcp.onchaindiligence.com/mcp"
}
}
}{
"mcpServers": {
"onchaindiligence-compliance": {
"type": "http",
"url": "https://mcp.onchaindiligence.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.1.0
What it does
An MCP server that exposes on-chain compliance checks—sanctions screening, OFAC name matching, and UK/US company verification—as tools that AI agents can call and pay for per use in USDC on Base via the x402 protocol. For developers building agents that need to perform compliance checks autonomously without maintaining API keys or subscriptions.
- Screen a wallet address against US/EU/UN sanctions lists before transacting with it.
- Check whether a person or company name matches OFAC SDN watchlists.
- Look up UK company registration details including status, incorporation date, and people with significant control.
Tools this server exposes
| Tool | Does |
|---|---|
| screen_wallet | Screen a wallet address against Chainalysis on-chain sanctions oracle covering US, EU, and UN lists. |
| screen_name | Fuzzy-match a person or company name against OFAC SDN names and strong aliases. |
| verify_uk_company | Look up a UK company by registration number to retrieve status, type, incorporation date, registered address, and people with significant control. |
| verify_us_company | Resolve a public US company through SEC EDGAR. |
| diligence | Run wallet and UK company checks in parallel without claiming a verified link between them. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.