mcpbeat Sign in

Counterparty Due Diligence MCP Server

not responding

Counterparty Due Diligence is listed as active in the registry but did not answer our last check. It exposes 1 tools.

One-call counterparty screen: sanctions, export, PEP, registry. $0.10/call via x402.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 23 days of history · worst day 0%
23 days agonow
0.0%
Uptime 24h
0 of 91 checks
1
Tools
read from the server
186 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 October 2026. No other catalogue keeps this.

17 Oct a tool description was rewritten counterparty_due_diligence

Counterparty Due Diligence does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add due-diligence --transport http https://due-diligence-production-1338.up.railway.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://due-diligence-production-1338.up.railway.app/mcp
~/.codex/config.toml
[mcp_servers.due-diligence]
url = "https://due-diligence-production-1338.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "due-diligence": {
      "url": "https://due-diligence-production-1338.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "due-diligence": {
      "type": "http",
      "url": "https://due-diligence-production-1338.up.railway.app/mcp"
    }
  }
}

Available tools 1

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

counterparty
counterparty_due_diligence
Screen a new counterparty (person or company) in one call before onboarding, contracting or paying it. Checks sanctions (OFAC, EU, UK; UN via EU/UK), the US Consolidated Screening List, PEP (Wikidata) and registries (GLEIF, Norway). Returns no_match, possible_match, confirmed_match or unable_to_determine with confidence, sources, coverage_limitations and a screening_signal (not a compliance approval). Use for a first-pass screen before human review. $0.10 per call, USDC on Base (x402).

Endpoints

URLTransportStateLatencyChecked
https://due-diligence-production-1338.up.railway.app/mcp streamable-http answering 186 ms 10 min ago

Alternatives to Counterparty Due Diligence

same job, measured the same way
agosint
by shveik

Company and domain due diligence for agents: registers, sanctions, VAT, domain. Pay per call.

10 tools answering
Canada Company Due Diligence Check
by domaranskyi

Due diligence on Canadian companies: registry status, sanctions and risk signals via Apify.

answering
APAC Licensed-Entity Lookup
by workers-regnotes-apac-license-lookup

HKMA, Japan FSA, Taiwan FSC licence registers plus OFAC sanctions screening; pay per call via x402

5 tools answering
P
POKT Agent Korea data (x402 paid)
by jsymen1290

Korean company due diligence, sanctions screening, Upbit/Bithumb events, HWP. Pay per call (x402).

29 tools answering
Stillos Kya
by stillmarcus24

Counterparty due-diligence infrastructure: OFAC screening, on-chain risk, signed verdicts.

81 installs/wk 1 tools answering
Dd
by cz-agents

Czech & EU due diligence in one call — facts, insolvency, sanctions, VAT, risk score, UBO chain.

114 installs/wk 12 tools answering
V
Veles Finance MCP
by fly-veles-finance-gateway

AI financial agent: due diligence, SEC 10-K, Kelly Criterion. Pay-per-call via x402 USDC.

104 installs/wk local only
Genesis402 by UnyKorn (x402 pay-per-call)
by fthtrading

Counterparty checks, sanctions screening, company lookup and 360+ pay-per-call APIs over x402.

79 installs/wk 22 tools answering

Counterparty Due Diligence — questions

Answers built from our own checks of this server.

What can Counterparty Due Diligence do?
It exposes 1 tools, read directly from the server on our last check. Among them: counterparty_due_diligence. 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 →
Is Counterparty Due Diligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 186 ms. The bar chart above shows every period we have measured.
Is Counterparty Due Diligence still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Counterparty Due Diligence as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Counterparty Due Diligence?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Counterparty Due Diligence need an API key?
No. Counterparty Due Diligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.