Remote MCP · Endpoint
Counterparty Due Diligence MCP server
No. Counterparty Due Diligence answered an MCP handshake 13 minutes ago.
UpLast checked 13 minutes ago
Server URL
https://due-diligence-production-1338.up.railway.app/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.pcp183/due-diligence
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 139 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 7.1% from 14 checks
- Described by its publisher as
- One-call counterparty screen: sanctions, export, PEP, registry. $0.10/call via x402.
- Repository
- https://github.com/pcp183/due-diligence
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 13 minutes ago | Handshake completed | 139 ms |
| 10 days ago | Failed - the server returned an HTTP error | — |
| 10 days ago | Failed - the server returned an HTTP error | — |
| 11 days ago | Failed - the server returned an HTTP error | — |
| 13 days ago | Failed - the server returned an HTTP error | — |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 15 days ago | Failed - the server returned an HTTP error | — |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 24 days ago | Failed - the server returned an HTTP error | — |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 28 days ago | Failed - the server returned an HTTP error | — |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 15.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Counterparty Due Diligence and makes no claim about it beyond what these checks measured.