Remote MCP · Endpoint
ZapSign MCP server
No. ZapSign answered an MCP handshake 2 hours ago.
UpLast checked 2 hours 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
- 102 ms
- Tools exposed
- 35 tools
- Uptime, last 30 days
- 4 checks from 4 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).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 102 ms |
| 6 hours ago | Handshake completed | 63 ms |
| 1 day ago | Handshake completed | 64 ms |
| 2 days ago | Handshake completed | 428 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 ZapSign and makes no claim about it beyond what these checks measured.