Remote MCP · Endpoint

ZeroWidth Napkin MCP server

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

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
ai.zerowidth/napkin
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
152 ms
Tools exposed
68 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Draw boards, write docs and sheets, and build decks with your brand in Napkin.
Listing
From the official MCP registry (active).
Recent checks of ZeroWidth Napkin
CheckedResultHandshake
1 hour agoHandshake completed152 ms
18 hours agoHandshake completed228 ms
2 days agoHandshake completed131 ms
4 days agoHandshake completed408 ms
6 days agoHandshake completed134 ms
9 days agoHandshake completed161 ms
11 days agoHandshake completed306 ms
13 days agoHandshake completed301 ms
15 days agoHandshake completed213 ms
17 days agoHandshake completed904 ms
20 days agoHandshake completed750 ms
21 days agoHandshake completed285 ms
23 days agoHandshake completed87 ms
24 days agoHandshake completed874 ms

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