SELISE Signature

com.selisesignature/signature · v0.4.0 · productivity

SELISE Signature is healthy: it completed an MCP handshake in 1871 ms and exposes 4 tools.

Prepare and send documents for electronic signature with SELISE Signature.

Endpoint: https://signaturemcp.selise.biz/mcp (streamable-http)

No repository listed · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count4
Latency1871 ms
Last checked (UTC)2026-10-16T00:00:19.422Z

Health history

Checked (UTC)StatusLatencyError
2026-10-16T00:00:19.422ZHealthy1871
2026-10-16T00:00:19.335ZHealthy1772
2026-10-14T21:45:52.779ZHealthy3807

Tools (4)

prepare_free_signature_documentPrepare a NEW free-signature document from one PDF without sending it. Accept Base64, a public HTTPS download URL, an existing SELISE storage file ID, a reference from the binary upload endpoint, or a ChatGPT attachment through chatgptFile. New bytes are uploaded; existing storage/upload references
send_prepared_signature_documentAdd field placements to an EXISTING prepared free-signature document and send it to its participants. This tool does not upload, prepare, or itself sign a document. Use only when sending is requested and preparation is confirmed; for a pending preparation, check status first. Reuse the matching docu
prepare_and_send_free_signature_documentPrepare a NEW free-signature document from one PDF, add placements, and send it in one workflow. Accept Base64, a public HTTPS download URL, an existing SELISE storage file ID, a reference from the binary upload endpoint, or a ChatGPT attachment through chatgptFile. Uploads new bytes or reuses the e
get_signature_document_statusRead document status events once using an actual documentId UUID. Use to check progress after preparation/sending, especially pending or UNKNOWN_OUTCOME. Does not upload, prepare, send, sign, or continuously poll. Returns {statuses: [...]} containing only distinct observed values: preparation_succes