Remote MCP · Endpoint

GoodSign MCP server

No. GoodSign answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://goodsign.io/mcp

The last check completed an MCP handshake.

Registry name
io.goodsign/goodsign
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
98 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Send documents for e-signature, track and remind signers, and download signed PDFs.
Listing
From the official MCP registry (active).
Recent checks of GoodSign
CheckedResultHandshake
1 day agoHandshake completed98 ms
3 days agoHandshake completed79 ms
5 days agoHandshake completed96 ms
6 days agoHandshake completed139 ms
8 days agoHandshake completed109 ms
9 days agoHandshake completed90 ms
10 days agoHandshake completed87 ms
13 days agoHandshake completed99 ms
14 days agoHandshake completed87 ms
16 days agoHandshake completed90 ms
18 days agoHandshake completed79 ms
19 days agoHandshake completed80 ms
20 days agoHandshake completed91 ms
21 days agoHandshake completed324 ms
21 days agoHandshake completed98 ms
22 days agoHandshake completed116 ms
24 days agoHandshake completed85 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 GoodSign and makes no claim about it beyond what these checks measured.