Remote MCP · Endpoint

ZapSign MCP server

No. ZapSign answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_zapsign

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/zapsign-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
204 ms
Tools exposed
35 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
ZapSign electronic document signing via the official API: create documents for signature (from PDF,
Repository
https://github.com/mcp-dir/zapsign-mcp
Listing
From the official MCP registry (active).
Recent checks of ZapSign
CheckedResultHandshake
1 hour agoHandshake completed204 ms
2 days agoHandshake completed345 ms
4 days agoHandshake completed34 ms
5 days agoHandshake completed39 ms
7 days agoHandshake completed161 ms
8 days agoHandshake completed84 ms
9 days agoHandshake completed159 ms
12 days agoHandshake completed70 ms
14 days agoHandshake completed64 ms
15 days agoHandshake completed370 ms
17 days agoHandshake completed43 ms
18 days agoHandshake completed189 ms
19 days agoHandshake completed83 ms
20 days agoHandshake completed102 ms
21 days agoHandshake completed63 ms
21 days agoHandshake completed64 ms
23 days agoHandshake completed428 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with ZapSign and makes no claim about it beyond what these checks measured.