Remote MCP · Endpoint

French Due Diligence MCP server

No. French Due Diligence answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp-fr.opendata-apis.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.Zansuken/french-due-diligence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
298 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Keyless French company checks (Sirene, BODACC, VIES, sanctions), DPE compliance, product recalls
Listing
From the official MCP registry (active).
Recent checks of French Due Diligence
CheckedResultHandshake
1 hour agoHandshake completed298 ms
4 days agoHandshake completed418 ms
14 days agoHandshake completed212 ms
15 days agoHandshake completed567 ms
15 days agoHandshake completed255 ms
17 days agoHandshake completed211 ms
18 days agoHandshake completed223 ms
19 days agoHandshake completed343 ms
20 days agoHandshake completed227 ms
21 days agoHandshake completed218 ms
23 days agoHandshake completed356 ms
25 days agoHandshake completed316 ms
28 days agoHandshake completed211 ms

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

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 French Due Diligence and makes no claim about it beyond what these checks measured.