OnChainDiligence MCP server
Which servers in the official MCP registry are OnChainDiligence's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-24
- Registry namecom.onchaindiligence/complianceverified in the MCP registry
The registry name sits under onchaindiligence.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools21
- Server calls itselfmcp-typescript server on vercel
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 204 ms.
- Its tools do every use case we checked: compare agent payment declarations against executor claims and observed settlement; verify receipts for supported onchain USDC transfers.
- Checked on 2 of the 7 days it takes to judge reliability.
Once connected
- Parameters are untyped or undescribed in 14 of 21 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- What an agent can do with it2 of 2 use cases
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer187 ms
- Space in an agent's context≈ 6,431 tokensthe definitions of all its tools (21), which an agent carries on every turn
- Tool definitionsB · 85 of 100
- Typed results0 of 21 toolsdeclared outputSchema: results come typed, read once
- Parameters without a type: in 5 of 21
- Parameters without a description: in 14 of 21
What an agent can do with it
- can do · compare agent payment declarations against executor claims and observed settlement
- can do · verify receipts for supported onchain USDC transfers
- not sure · check wallet address activity against existing workspace evidence
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
screen_walletExact match of an EVM wallet address against the digital currency address identifiers on the official US Treasury OFAC SDN List (validated snapshot, refreshed hourly). Returns signed listed / not_listed, the SDN entry, dataset provenance…
screen_nameOFAC 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…
verify_uk_companyUK company KYB lookup via the official Companies House register. Given a UK registration number, returns legal status (active/dissolved), company type, incorporation date, registered office, and people with significant control (PSC /…
verify_us_companyUS public company verification via SEC EDGAR. Given a ticker, CIK, or company name, returns entity name, CIK, industry (SIC), state of incorporation, exchanges/tickers, address, and latest SEC filing. Ambiguous names return candidates…
diligenceCombined counterparty due diligence in one call: an exact OFAC SDN digital-currency-address screen of an EVM wallet AND a UK Companies House KYB lookup (status, type, PSC / beneficial owners), in parallel. Returns both independent results…
preflight_paymentCall BEFORE an agent authorizes an autonomous payment. Evaluates it against your policy (max amount, allowed networks/assets, expected recipient, allowed origins) and returns a signed PREFLIGHT receipt -- ALLOW, REQUIRE_APPROVAL, or…
inspect_paymentFREE. Pure deterministic inspection of a proposed payment against structured policy (amount/network/asset/recipient/resource) — no external evidence, no sanctions screening, no cryptographic signing, no receipt. Returns the same ALLOW /…
inspect_allowanceFREE. Deterministically inspect an ERC-20 allowance/revocation request against explicit network/token/spender/value policy. No wallet action, no signing, no chain read unless a separately requested preflight asks for it.
preflight_allowanceCall BEFORE an agent asks its wallet to approve or revoke a Base USDC ERC-20 allowance. OCD evaluates strict policy and returns a signed portable allowance artifact. ALLOW is policy only, never wallet authority.
observe_allowanceGiven a signed OCD allowance preflight artifact and submitted Base transaction hash, independently inspect its canonical-USDC Approval event, Base safe-head finality, and historical allowance state. OCD never executes the transaction.
inspect_swapFREE. Deterministically inspect a narrow Base USDC-to-WETH direct Uniswap V3 swap against explicit policy. No wallet action or signing.
preflight_swapCall BEFORE an agent asks its wallet to execute a narrow Base USDC-to-WETH direct Uniswap V3 swap. OCD returns a signed portable policy artifact. ALLOW is policy only, never wallet authority.
observe_swapGiven a signed OCD swap preflight artifact and Base transaction hash, independently inspect direct Uniswap V3 exactInputSingle calldata, ERC-20 transfers, and Base safe-head finality. OCD never executes the swap.
inspect_bridgeFREE. Deterministically inspect a narrow Circle CCTP V2 Base-to-Ethereum native-USDC bridge request against explicit policy. No wallet action, no signing, no chain read.
preflight_bridgeCall BEFORE an agent asks its wallet to bridge Base USDC to Ethereum via Circle CCTP V2 (depositForBurn). OCD evaluates strict policy and returns a signed portable bridge artifact. ALLOW is policy only, never wallet authority.
observe_bridgeGiven a signed OCD bridge preflight artifact, the Base depositForBurn transaction hash, and (once available) the Ethereum receiveMessage transaction hash, independently observe both chains, verify the CCTP message identity matches, and…
inspect_stakingFREE. Deterministically inspect a narrow Ethereum Lido stETH submit request against explicit policy. No wallet action, signing, or chain read.
preflight_stakingCall BEFORE an agent asks its wallet to submit ETH to Lido stETH. OCD evaluates strict policy and returns a signed portable staking artifact. ALLOW is policy only, never wallet authority.
observe_stakingGiven a signed OCD staking preflight artifact and Ethereum transaction hash, independently inspect the canonical Lido Submitted event, transaction sender/value, optional minted shares, and Ethereum finalized-head finality. OCD never…
get_receiptLook up a public OCD receipt by its exact receipt_id (format "OCD-RCP-XXXX-XXXX-XXXX-XXXX"). Free, no payment. Returns the complete signed receipt envelope, or a structured not-found/unavailable reason -- never a guess. A private…
verify_receiptIndependently checks whether a receipt is cryptographically VALID, INVALID, or UNVERIFIABLE, with a reason code. Free, no payment. Pass EITHER receipt_id (looks it up first, must be public) OR a complete receipt envelope you already hold…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"compliance": {
"type": "http",
"url": "https://mcp.onchaindiligence.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http onchaindiligence https://mcp.onchaindiligence.com/mcpclaude.ai, ChatGPT and other clients: add https://mcp.onchaindiligence.com/mcp as a custom connector in the settings.
- com.onchaindiligence/payment-evidenceanswers, 4 toolsverified in the MCP registry
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.