OnchainDiligence MCP Server

com.onchaindiligence/compliance

answering

OnchainDiligence is answering right now. Last checked 5 min ago. It exposes 5 tools. Last commit 8 Jul 2026.

Pay-per-call compliance via x402: wallet sanctions, OFAC name, UK + US company verification.

Uptime history 41 hours of history · worst hour 0%

41 hours agonow

76.9%

Uptime 24h

70 of 91 checks

Tools

read from the server

313 ms

Response time

average over 24h

Stars

last commit 8 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add compliance --transport http https://mcp.onchaindiligence.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "compliance": {
      "url": "https://mcp.onchaindiligence.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.compliance]
url = "https://mcp.onchaindiligence.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "compliance": {
      "url": "https://mcp.onchaindiligence.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "compliance": {
      "url": "https://mcp.onchaindiligence.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

screen

screen_name

OFAC name screening: fuzzy-match a person or company name against the official US Treasury OFAC Specially Designated Nationals (SDN) list (primary names + strong aliases). Returns scored candidate matches with the matched name, SDN type, and program. SCOPE: this is a screening aid for AML / KYC / sanctions compliance — a match is a candidate to investigate with secondary identifiers (DOB, nationality, ID), NOT a determination. Weak AKAs are not screened, per OFAC guidance.

screen_wallet

Sanctions screening for a crypto wallet address. Checks an EVM address against the Chainalysis on-chain sanctions oracle, which covers OFAC SDN, EU, and UN designated addresses (including Tornado Cash and other sanctioned protocols). Returns a clear sanctioned / not-sanctioned result with the matching program. Use for AML compliance, counterparty due diligence, and payment screening before sending USDC or any funds to an address.

verify

verify_uk_company

UK company verification and KYB (know-your-business) lookup via the official Companies House register. Given a UK company registration number, returns legal status (active / dissolved), company type, incorporation date, registered office address, and the people with significant control (PSC / beneficial owners). Use for KYB onboarding, supplier and counterparty due diligence, and confirming a UK business is real, active, and who controls it. Authoritative UK government open data.

verify_us_company

US public company verification via the SEC EDGAR system. Given a ticker, SEC CIK, or company name, returns the registered entity name, CIK, industry (SIC code), state of incorporation, listed exchanges and tickers, business address, and most recent SEC filing. SCOPE: EDGAR covers SEC-registered PUBLIC companies and funds only — NOT private US companies, which register at the state level. Use for KYB and counterparty due diligence on listed US entities. Authoritative US government open data.

diligence

diligence

Combined counterparty due diligence in one call: runs sanctions screening on a crypto wallet (Chainalysis oracle — OFAC SDN, EU, UN) AND a UK Companies House KYB lookup (status, type, PSC / beneficial owners) in parallel. Built for compliance agents vetting a counterparty that has both an on-chain wallet and a UK company. Returns both independent results, plus an explicit disclaimer that no verified link between the wallet and the company is established by the data.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.onchaindiligence.com/mcp	streamable-http	answering	259 ms	5 min ago

OnchainDiligence — questions

Answers built from our own checks of this server.

What can OnchainDiligence do?

It exposes 5 tools, read directly from the server on our last check. Among them: diligence, screen_name, screen_wallet, verify_uk_company, verify_us_company. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is OnchainDiligence mostly used for?

Its tools cluster around screen and verify. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is OnchainDiligence working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 70 of 91 checks got a reply (76.9%), average response time 313 ms. The bar chart above shows every period we have measured.

How do I connect OnchainDiligence?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does OnchainDiligence need an API key?

No. OnchainDiligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is OnchainDiligence?

It answers our handshake in 313 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is OnchainDiligence open source?

Yes — it is published under the NOASSERTION licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.