OnchainDiligence vs Sanctions Screening

In-depth architectural comparison of the OnchainDiligence and Sanctions Screening MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose OnchainDiligence when:

• You need dedicated capabilities in the Finance & Fintech domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore OnchainDiligence Details

S

Choose Sanctions Screening when:

• You need dedicated capabilities in the Finance & Fintech domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Sanctions Screening Details

Feature & Specification Comparison

Specification	OnchainDiligence Finance & Fintech	S Sanctions Screening Finance & Fintech
Summary	Pay-per-call sanctions screening and UK company checks for agents, paid in USDC via x402.	Deterministic sanctions screening for AI agents: OFAC, UN, EU, UK lists. x402 or API-key pay.
Category & Scope	Finance & Fintech	Finance & Fintech

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "onchaindiligence": {
      "url": "https://x402.org"
    }
  }
}

{
  "mcpServers": {
    "sanctions-screening": {
      "url": "https://watchtower-api.com"
    }
  }
}

Related MCP Server Comparisons