Remote MCP · Endpoint

Bodacc MCP server

Yes, as of 2 hours ago: the request timed out.

DownLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/bodacc/mcp

The last check failed: the request timed out.

Registry name
io.github.pipeworx-io/bodacc
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
44 tools
Uptime, last 30 days
80.0% from 15 checks
Described by its publisher as
BODACC MCP — French official business-events bulletin (keyless).
Listing
From the official MCP registry (active).
Recent checks of Bodacc
CheckedResultHandshake
2 hours agoFailed - the request timed out—
2 days agoHandshake completed1.39 s
4 days agoHandshake completed213 ms
6 days agoHandshake completed1.42 s
7 days agoFailed - the request timed out—
9 days agoHandshake completed2.37 s
10 days agoHandshake completed1.76 s
11 days agoHandshake completed1.22 s
13 days agoHandshake completed53 ms
15 days agoHandshake completed1.09 s
17 days agoHandshake completed1.31 s
19 days agoFailed - the request timed out—
20 days agoHandshake completed139 ms
21 days agoHandshake completed40 ms
22 days agoHandshake completed945 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 Bodacc and makes no claim about it beyond what these checks measured.