Remote MCP · Endpoint

ZeroWidth Workbench MCP server

No. ZeroWidth Workbench answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.zerowidth.ai/mcp/x/workbench

The last check completed an MCP handshake.

Registry name
ai.zerowidth/workbench
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
153 ms
Tools exposed
61 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Build, run and publish Workbench flows, tasks, shims and knowledge bases.
Listing
From the official MCP registry (active).
Recent checks of ZeroWidth Workbench
CheckedResultHandshake
1 hour agoHandshake completed153 ms
22 hours agoHandshake completed247 ms
2 days agoHandshake completed213 ms
4 days agoHandshake completed243 ms
7 days agoHandshake completed593 ms
9 days agoHandshake completed666 ms
11 days agoHandshake completed231 ms
13 days agoHandshake completed1.46 s
16 days agoHandshake completed1.04 s
18 days agoHandshake completed239 ms
20 days agoHandshake completed264 ms
22 days agoHandshake completed754 ms
23 days agoHandshake completed731 ms
24 days agoHandshake completed1.10 s

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

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