Remote MCP · Endpoint

SELISE Signature MCP server

No. SELISE Signature answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://signaturemcp.selise.biz/mcp

The last check completed an MCP handshake.

Registry name
com.selisesignature/signature
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
356 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Prepare and send documents for electronic signature with SELISE Signature.
Listing
From the official MCP registry (active).
Recent checks of SELISE Signature
CheckedResultHandshake
1 hour agoHandshake completed356 ms
2 days agoHandshake completed328 ms
4 days agoHandshake completed321 ms
6 days agoHandshake completed342 ms
8 days agoHandshake completed310 ms
10 days agoHandshake completed322 ms
13 days agoHandshake completed387 ms
14 days agoHandshake completed364 ms
16 days agoHandshake completed412 ms
17 days agoHandshake completed331 ms
18 days agoHandshake completed300 ms
21 days agoHandshake completed328 ms
22 days agoHandshake completed328 ms
24 days agoHandshake completed323 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 SELISE Signature and makes no claim about it beyond what these checks measured.