Remote MCP · Endpoint

Ares Cz MCP server

No. Ares Cz answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://gateway.pipeworx.io/ares-cz/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/ares-cz
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Czech business register (ARES) — look up any Czech company or sole trader by IČO or by name, from…
Listing
From the official MCP registry (active).
Recent checks of Ares Cz
CheckedResultHandshake
5 hours agoHandshake completed52 ms
2 days agoHandshake completed75 ms
4 days agoHandshake completed81 ms
6 days agoHandshake completed64 ms
8 days agoHandshake completed68 ms
9 days agoHandshake completed61 ms
10 days agoHandshake completed1.48 s
11 days agoHandshake completed1.54 s
14 days agoHandshake completed1.01 s
16 days agoHandshake completed886 ms
17 days agoHandshake completed1.55 s
19 days agoHandshake completed59 ms
20 days agoHandshake completed41 ms
21 days agoHandshake completed43 ms
22 days agoHandshake completed59 ms
22 days agoHandshake completed52 ms

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

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