Remote MCP · Endpoint

md2sign MCP server

No. md2sign answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://md2sign.com/mcp

The last check completed an MCP handshake.

Registry name
com.md2sign/md2sign
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
142 ms
Tools exposed
27 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Send markdown contracts for legally binding e-signatures. Draft, preview, send and track signing.
Listing
From the official MCP registry (active).
Recent checks of md2sign
CheckedResultHandshake
9 hours agoHandshake completed142 ms
4 days agoHandshake completed209 ms
7 days agoHandshake completed152 ms

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

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