Remote MCP · Endpoint

KYB due diligence and company checks MCP server

No. KYB due diligence and company checks answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://api.boscolabs.dev/mcp?tools=counterparty_check,company_check,company_accounts,sanctions_screening,vat_iban_check,identifier_resolver,plan_official_records_query

The last check completed an MCP handshake.

Registry name
io.github.Bosco-Labs/kyb-due-diligence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
125 ms
Tools exposed
11 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
KYB compliance checks: Companies House and EU registers, insolvency, sanctions, VAT, IBAN, LEI
Listing
From the official MCP registry (active).
Recent checks of KYB due diligence and company checks
CheckedResultHandshake
3 hours agoHandshake completed125 ms
4 days agoHandshake completed144 ms
7 days agoHandshake completed122 ms

The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.

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 KYB due diligence and company checks and makes no claim about it beyond what these checks measured.