# OnchainDiligence (remote · mcp.onchaindiligence.com)

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

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `mcp.onchaindiligence.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-onchaindiligence-compliance/mcp.md), [page](https://verifymcp.io/servers/com-onchaindiligence-compliance/mcp)

## Channel facts

- Endpoint: `https://mcp.onchaindiligence.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 696 tokens (~139/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-onchaindiligence-compliance": {
      "type": "remote",
      "url": "https://mcp.onchaindiligence.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-onchaindiligence-compliance --url https://mcp.onchaindiligence.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-onchaindiligence-compliance:
    url: "https://mcp.onchaindiligence.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-onchaindiligence-compliance": {
      "type": "http",
      "url": "https://mcp.onchaindiligence.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (5)

### `screen_wallet` (~116 tokens)

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.

Input parameters:

- `address` (string, required): EVM wallet address (0x + 40 hex) to sanctions-screen

### `screen_name` (~164 tokens)

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.

Input parameters:

- `name` (string, required): Person or company name to screen against the OFAC SDN list
- `threshold` (number): Optional match confidence cutoff 0.5–1.0 (default 0.85). Lower = more candidates, more false positives.

### `verify_uk_company` (~124 tokens)

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.

Input parameters:

- `companyNumber` (string, required): UK Companies House registration number to verify, e.g. 00000006

### `verify_us_company` (~151 tokens)

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.

Input parameters:

- `query` (string, required): US public company ticker, SEC CIK, or company name — e.g. "AAPL", "0000320193", or "Apple Inc"

### `diligence` (~141 tokens)

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.

Input parameters:

- `company` (string, required): UK Companies House registration number to verify
- `wallet` (string, required): EVM wallet address (0x + 40 hex) to sanctions-screen

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-onchaindiligence-compliance/mcp#diagnostics

## Score history

- 2026-08-04: 70
- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://mcp.onchaindiligence.com/mcp
- Repository: https://github.com/Qazza1/onchaindiligence-mcp
- Website: https://onchaindiligence.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-onchaindiligence-compliance/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-onchaindiligence-compliance/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-onchaindiligence-compliance/mcp