Remote MCP · Endpoint

auregistre MCP server

No. auregistre answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://auregistre.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.auregistre/auregistre
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
150 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
French companies: dated changes and insolvencies (BODACC), filed accounts by year (INPI). No key.
Listing
From the official MCP registry (active).
Recent checks of auregistre
CheckedResultHandshake
1 hour agoHandshake completed150 ms
2 days agoHandshake completed116 ms
4 days agoHandshake completed30 ms
5 days agoHandshake completed81 ms
7 days agoHandshake completed40 ms
8 days agoHandshake completed321 ms
9 days agoHandshake completed33 ms
12 days agoHandshake completed42 ms
13 days agoHandshake completed45 ms
15 days agoHandshake completed67 ms
16 days agoHandshake completed85 ms
18 days agoHandshake completed35 ms
19 days agoHandshake completed34 ms
20 days agoHandshake completed31 ms
20 days agoHandshake completed76 ms
21 days agoHandshake completed39 ms
22 days agoHandshake completed85 ms

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

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