OnchainDiligence
REMOTE · MCP.ONCHAINDILIGENCE.COM · SCANNED AUG 3
Pay-per-call compliance via x402: wallet sanctions, OFAC name, UK + US company verification.
Available components
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. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.onchaindiligence.com
claude mcp add --transport http com-onchaindiligence-compliance https://mcp.onchaindiligence.com/mcp
[mcp_servers.com-onchaindiligence-compliance] url = "https://mcp.onchaindiligence.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-onchaindiligence-compliance": {
"type": "remote",
"url": "https://mcp.onchaindiligence.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-onchaindiligence-compliance --url https://mcp.onchaindiligence.com/mcp --transport streamable-http
mcp_servers:
com-onchaindiligence-compliance:
url: "https://mcp.onchaindiligence.com/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +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.
- 29 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.onchaindiligence.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.onchaindiligence.com | CN=YR1,O=Let's Encrypt,C=US | 20 Jun 2026 | 18 Sept 2026 | RSA 2048 | SHA256-RSA | 58c8d0b7ae7875dfd38a0ba0a8a16b1b941 |
| SANs: mcp.onchaindiligence.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of mcp.onchaindiligence.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onchaindiligence.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.onchaindiligence.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.onchaindiligence.com/mcp | HTTPS enforced | 308 | https://mcp.onchaindiligence.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
diligence ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | UK Companies House registration number to verify |
| wallet | string | yes | EVM wallet address (0x + 40 hex) to sanctions-screen |
No output schema declared.
No examples provided.
screen_name ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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. |
No output schema declared.
No examples provided.
screen_wallet ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM wallet address (0x + 40 hex) to sanctions-screen |
No output schema declared.
No examples provided.
verify_uk_company ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companyNumber | string | yes | UK Companies House registration number to verify, e.g. 00000006 |
No output schema declared.
No examples provided.
verify_us_company ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | US public company ticker, SEC CIK, or company name — e.g. "AAPL", "0000320193", or "Apple Inc" |
No output schema declared.
No examples provided.