Remote MCP · Endpoint

Dock MCP server

No. Dock answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://trydock.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.trydock/dock
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
87 ms
Tools exposed
80 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
AI workspace for you, your team, and every agent. Tables, docs (images, 4K video), formulas.
Listing
From the official MCP registry (active).
Recent checks of Dock
CheckedResultHandshake
7 hours agoHandshake completed87 ms
2 days agoHandshake completed65 ms
4 days agoHandshake completed498 ms
5 days agoHandshake completed72 ms
7 days agoHandshake completed94 ms
8 days agoHandshake completed74 ms
9 days agoHandshake completed131 ms
12 days agoHandshake completed387 ms
13 days agoHandshake completed450 ms
15 days agoHandshake completed1.61 s
16 days agoHandshake completed324 ms
17 days agoHandshake completed335 ms
19 days agoHandshake completed333 ms
19 days agoHandshake completed384 ms
20 days agoHandshake completed72 ms
21 days agoHandshake completed110 ms
22 days agoHandshake completed71 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 Dock and makes no claim about it beyond what these checks measured.