Remote MCP · Endpoint

docks Produktberatung MCP server

No. docks Produktberatung answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent.docks.io/mcp

The last check completed an MCP handshake.

Registry name
io.docks/agent
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
394 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Maschinendokumentation per QR-Code (EU-MVO 2023/1230): belegte Fakten prüfen, Pilotanfrage stellen.
Listing
From the official MCP registry (active).
Recent checks of docks Produktberatung
CheckedResultHandshake
1 hour agoHandshake completed394 ms
3 days agoHandshake completed336 ms
12 days agoHandshake completed335 ms
13 days agoHandshake completed355 ms
15 days agoHandshake completed339 ms
15 days agoHandshake completed341 ms
17 days agoHandshake completed347 ms
18 days agoHandshake completed334 ms
18 days agoHandshake completed333 ms
20 days agoHandshake completed356 ms
22 days agoHandshake completed331 ms
25 days agoHandshake completed376 ms
27 days agoHandshake completed338 ms
29 days agoHandshake completed353 ms

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