Remote MCP · Endpoint

Bodacc MCP server

No. Bodacc answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/bodacc
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
621 ms
Tools exposed
48 tools
Uptime, last 30 days
92.9% from 14 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
8 hours agoHandshake completed621 ms
10 days agoHandshake completed197 ms
11 days agoHandshake completed85 ms
12 days agoHandshake completed112 ms
13 days agoHandshake completed111 ms
15 days agoHandshake completed154 ms
15 days agoHandshake completed66 ms
16 days agoHandshake completed232 ms
17 days agoHandshake completed748 ms
19 days agoHandshake completed967 ms
22 days agoHandshake completed1.07 s
24 days agoHandshake completed1.11 s
27 days agoHandshake completed1.13 s
29 days agoFailed - the request timed out—

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

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.