# SELISE Signature (remote · signaturemcp.selise.biz) Prepare and send documents for electronic signature with SELISE Signature. - Trust score: 73/100 (medium) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-25 ## Components - remote · `signaturemcp.selise.biz`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-selisesignature-signature/signaturemcp.md), [page](https://verifymcp.io/servers/com-selisesignature-signature/signaturemcp) ## Channel facts - Endpoint: `https://signaturemcp.selise.biz/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `0.4.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-25. - **Endpoint Security**: 57/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_prepared_signature_document). - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 57/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 5553 tokens (~1388/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 83/100 - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the SELISE Signature MCP server? SELISE Signature is a hosted endpoint at https://signaturemcp.selise.biz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http com-selisesignature-signature 'https://signaturemcp.selise.biz/mcp' ``` ### Cursor ```json { "mcpServers": { "com-selisesignature-signature": { "url": "https://signaturemcp.selise.biz/mcp" } } } ``` ### VS Code ```json { "servers": { "com-selisesignature-signature": { "type": "http", "url": "https://signaturemcp.selise.biz/mcp" } } } ``` ### Codex ```toml [mcp_servers.com-selisesignature-signature] url = "https://signaturemcp.selise.biz/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-selisesignature-signature": { "type": "remote", "url": "https://signaturemcp.selise.biz/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-selisesignature-signature --url 'https://signaturemcp.selise.biz/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-selisesignature-signature: url: "https://signaturemcp.selise.biz/mcp" ``` ### Netclaw ```json { "McpServers": { "com-selisesignature-signature": { "Transport": "http", "Url": "https://signaturemcp.selise.biz/mcp" } } } ``` ### Vellum ```bash assistant mcp add com-selisesignature-signature -t streamable-http -u 'https://signaturemcp.selise.biz/mcp' ``` ### Other ```json { "mcpServers": { "com-selisesignature-signature": { "type": "http", "url": "https://signaturemcp.selise.biz/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-25 (score 73, +1) No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-23 (score 72, +1) No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-21 (score 71, +1) No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-20 (score 70, 0) - [security] The server rewrote its instructions, which are the text every model session reads ### 2026-10-18 (score 70, 0) - [security] Tool “prepare_and_send_free_signature_document” rewrote its description, which is the text the model reads - [security] Tool “prepare_free_signature_document” rewrote its description, which is the text the model reads - [cosmetic] “prepare_and_send_free_signature_document” reworded the description of “chatgptFile” - [cosmetic] “prepare_free_signature_document” reworded the description of “chatgptFile” ### 2026-10-17 (score 70, +1) No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-15 (score 69, +1) No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-13 (score 68, +1) No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (4) ### `prepare_free_signature_document` (~1667 tokens) Prepare free signature document Prepare 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 are reused. Use when preparation is requested or placements are not ready; do not call again for an existing or pending document. Provide exactly ONE file source: documentBase64 (raw standard Base64), documentUrl (public HTTPS PDF download URL, including a temporary signed URL), storageFileId (an existing SELISE storage PDF accessible to this server), uploadId (the exact short-lived reference returned by this server's HTTP POST /uploads), or chatgptFile (the host-provided file object for a PDF attached in ChatGPT). chatgptFile is exclusively for ChatGPT's attachment integration. Use it only when ChatGPT supplies the attachment object through openai/fileParams, including its download_url and file_id. Other clients, including Claude and Gemini, must not use this field or construct an equivalent object. They must use documentBase64, documentUrl, storageFileId, or uploadId, according to the file access available to them. If no supported source is available, ask the user for one; never fabricate file content, URLs, or identifiers. Do not combine sources, invent file content or IDs, or pass local paths to the server. A bare ChatGPT attachment ID is not a documentUrl or storageFileId. For binary upload, POST multipart/form-data with one file part named file to /uploads on this server's HTTP deployment, then use the returned uploadId before expiresAt; uploading does not prepare or send a document. Raw application/pdf uploads with a fileName query parameter are also accepted. The uploadId is valid for one hour; keep it private. Source PDFs are validated consistently. documentUrl must return PDF bytes without additional authentication headers; the server does not use browser cooki… Input parameters: - `chatgptFile` (object): File source option 5 - ChatGPT only. Claude, Gemini, and other MCP clients must omit this field and use documentBase64, documentUrl, storageFileId, or uploadId instead. Requires the actual user-attac… - `documentBase64` (string): File source option 1: actual PDF bytes encoded as raw standard Base64. Whitespace is ignored; no data URL, placeholder, local path, or fabricated content. Omit all other file sources when using this… - `documentUrl` (string): File source option 2: public HTTPS link that returns the actual PDF, optionally with a short-lived signed query string. No login page, browser cookies, custom authentication headers, local/private ad… - `fileName` (string, required): PDF filename, 1-255 characters, ending in .pdf (case-insensitive). Required for every source. Use a filename, not a path or URL. - `language` (string): Document workflow language. Supported values: en, en-US, de, de-DE. Defaults to en-US; this does not translate the uploaded PDF. - `ownerEmail` (string, required): Document owner's valid email, without surrounding whitespace. Must match an email in signatories after lowercase normalization. Being the owner does not automatically make someone a signer; preserve… - `receiveRolloutEmail` (boolean): Whether the document owner should receive the rollout email when the document is sent. Defaults to true. Setting this during preparation does not send the document. - `signatories` (array, required): Complete participant list, including the owner; at least one entry. ownerEmail must match one of the signatories' emails. Signatory emails must be unique (case-insensitive). Provide a positive intege… - `storageFileId` (string): File source option 3: exact existing SELISE storage file ID accessible using this server's configured credentials. It is not a documentId, client-specific attachment ID, or uploadId. Use an original… - `title` (string, required): Document title; required and nonempty after trimming. - `uploadId` (string): File source option 4: exact signed reference returned by this server's POST /uploads endpoint. Valid for one hour, until its expiresAt; do not alter it or replace it with a storage ID. Omit the other… ### `send_prepared_signature_document` (~1058 tokens) Send prepared signature document Add 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 documentId and fileId from preparation. All coordinate arrays apply to that single PDF and must refer to its existing participants. The server downloads the current PDF to read page dimensions for conversion; it does not discover intended field locations or retrieve participants. Obtain the participants and intended placements before calling. This tool uses only the prepared document's fileId, not documentBase64, documentUrl, storageFileId, uploadId, or chatgptFile. Maximum downloaded PDF size: 26214400 bytes. To start a new document from any of the five file sources, use a preparation tool instead. Set coordinateSystem to page_percent. ALL field types use the same page-relative percentages: (0,0) is the top-left of the visible page, x increases rightward, y increases downward; 100 is the full page width or height, not 1. pageNumber is zero-based (0 is the first page). x/width are percentages of page width; y/height are percentages of page height. Positions must be >= 0, sizes > 0, x + width <= 100 and y + height <= 100. Example: x=10,y=80,width=30,height=10 starts 10% from the left and 80% from the top, covering 30% of page width and 10% of its height. The server reads each PDF page and handles backend units and field-specific conversions. Do not supply pixels, PDF points, or backend coordinates, or guess a placement from an unrelated image. Use the actual visible page and the user's intended field location. Unrepresentable placements, unreadable PDFs, 180-degree rotated placement pages, and text fields on rotated/cropped pages are rejected before sending; provide a flattened PDF if requested by the error. Provide at least one signatureCoordinates entry; optional coordinate… Input parameters: - `coordinateSystem` (string, required): Required: page_percent. All positions and sizes use 0-100 percentages of the visible PDF page, from its top-left. This explicit marker prevents old pixel/backend coordinates from being misinterpreted… - `documentId` (string, required): Exact documentId returned by preparation for the existing document to send. Confirm preparation succeeded before calling. Do not invent an ID or substitute a fileId, operationId, or trackingId. - `fileId` (string, required): Exact fileId for the PDF in that prepared document, returned by preparation. Every supplied coordinate applies to this one file. Do not use a documentId, local path, or URL. - `signatureCoordinates` (array, required): Required nonempty signature-placement list for this PDF. In the combined tool, every signer needs at least one entry and every entry must refer to a supplied participant. For send-only, use the prepa… - `simpleImageCoordinates` (array): Optional simple-image placements for this PDF; defaults to []. Each entry requires a verified type and participant/page/position/size fields. - `stampPostInfoCoordinates` (array): Optional post-signing information placements for this PDF; defaults to []. Each entry requires verified entityName/propertyName and participant/page/position/size fields. - `textFieldCoordinates` (array): Optional text placements for this PDF; omit or use [] when none are requested. Each entry requires propertyName and participant/page/position/size fields. ### `prepare_and_send_free_signature_document` (~2270 tokens) Prepare and send free signature document Prepare 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 existing storage file. Use only when sending is requested and all participant details and actual PDF placements are known. For an already prepared document, use send_prepared_signature_document instead. This tool does not itself sign the PDF. Provide exactly ONE file source: documentBase64 (raw standard Base64), documentUrl (public HTTPS PDF download URL, including a temporary signed URL), storageFileId (an existing SELISE storage PDF accessible to this server), uploadId (the exact short-lived reference returned by this server's HTTP POST /uploads), or chatgptFile (the host-provided file object for a PDF attached in ChatGPT). chatgptFile is exclusively for ChatGPT's attachment integration. Use it only when ChatGPT supplies the attachment object through openai/fileParams, including its download_url and file_id. Other clients, including Claude and Gemini, must not use this field or construct an equivalent object. They must use documentBase64, documentUrl, storageFileId, or uploadId, according to the file access available to them. If no supported source is available, ask the user for one; never fabricate file content, URLs, or identifiers. Do not combine sources, invent file content or IDs, or pass local paths to the server. A bare ChatGPT attachment ID is not a documentUrl or storageFileId. For binary upload, POST multipart/form-data with one file part named file to /uploads on this server's HTTP deployment, then use the returned uploadId before expiresAt; uploading does not prepare or send a document. Raw application/pdf uploads with a fileName query parameter are also accepted. The uploadId is valid for one hour; keep it private. Source PDFs are validated consistently. do… Input parameters: - `chatgptFile` (object): File source option 5 - ChatGPT only. Claude, Gemini, and other MCP clients must omit this field and use documentBase64, documentUrl, storageFileId, or uploadId instead. Requires the actual user-attac… - `coordinateSystem` (string, required): Required: page_percent. All positions and sizes use 0-100 percentages of the visible PDF page, from its top-left. This explicit marker prevents old pixel/backend coordinates from being misinterpreted… - `documentBase64` (string): File source option 1: actual PDF bytes encoded as raw standard Base64. Whitespace is ignored; no data URL, placeholder, local path, or fabricated content. Omit all other file sources when using this… - `documentUrl` (string): File source option 2: public HTTPS link that returns the actual PDF, optionally with a short-lived signed query string. No login page, browser cookies, custom authentication headers, local/private ad… - `fileName` (string, required): PDF filename, 1-255 characters, ending in .pdf (case-insensitive). Required for every source. Use a filename, not a path or URL. - `language` (string): Document workflow language. Supported values: en, en-US, de, de-DE. Defaults to en-US; this does not translate the uploaded PDF. - `ownerEmail` (string, required): Document owner's valid email, without surrounding whitespace. Must match an email in signatories after lowercase normalization. Being the owner does not automatically make someone a signer; preserve… - `receiveRolloutEmail` (boolean): Whether the document owner should receive the rollout email when the document is sent. Defaults to true. Setting this during preparation does not send the document. - `signatories` (array, required): Complete participant list, including the owner; at least one entry. ownerEmail must match one of the signatories' emails. Signatory emails must be unique (case-insensitive). Provide a positive intege… - `signatureCoordinates` (array, required): Required nonempty signature-placement list for this PDF. In the combined tool, every signer needs at least one entry and every entry must refer to a supplied participant. For send-only, use the prepa… - `simpleImageCoordinates` (array): Optional simple-image placements for this PDF; defaults to []. Each entry requires a verified type and participant/page/position/size fields. - `stampPostInfoCoordinates` (array): Optional post-signing information placements for this PDF; defaults to []. Each entry requires verified entityName/propertyName and participant/page/position/size fields. - `storageFileId` (string): File source option 3: exact existing SELISE storage file ID accessible using this server's configured credentials. It is not a documentId, client-specific attachment ID, or uploadId. Use an original… - `textFieldCoordinates` (array): Optional text placements for this PDF; omit or use [] when none are requested. Each entry requires propertyName and participant/page/position/size fields. - `title` (string, required): Document title; required and nonempty after trimming. - `uploadId` (string): File source option 4: exact signed reference returned by this server's POST /uploads endpoint. Valid for one hour, until its expiresAt; do not alter it or replace it with a storage ID. Omit the other… ### `get_signature_document_status` (~328 tokens) Get signature document status Read 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_success (preparation succeeded), preparation_failed (preparation failed), sending_success (dispatch succeeded, not completed signing), sending_failed (dispatch failed), completed (document completion recorded). These are historical observations, not one current state. Success and failure can both appear; array order does not establish chronology. An empty list means no recognized events were returned: it does not prove existence, failure, completion, or that resubmission is safe. Other events, including cancellation, expiration, and individual-signer progress, are omitted; this is not a complete lifecycle report. Returns no timestamps, signer details, download URLs, or signing links. Request/authentication failures return an error, not an empty status list. If polling is needed, space checks by at least 3 seconds and avoid concurrent polling of the same document. A status check does not authorize retrying a state-changing tool. Use only the declared fields. Ask for missing facts instead of inventing values. Service credentials are configured on the server and must not be included in tool arguments. Input parameters: - `documentId` (string, required): Document UUID returned by a previous preparation/submission or supplied from a trusted source. Use the exact documentId, not fileId, trackingId, or operationId. Do not generate a placeholder UUID; fo… ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-selisesignature-signature/signaturemcp#diagnostics ## Score history - 2026-10-25: 73 - 2026-10-24: 72 - 2026-10-23: 72 - 2026-10-22: 71 - 2026-10-21: 71 - 2026-10-20: 70 - 2026-10-19: 70 - 2026-10-18: 70 - 2026-10-17: 70 - 2026-10-16: 69 - 2026-10-15: 69 - 2026-10-14: 68 - 2026-10-13: 68 - 2026-10-12: 67 - 2026-10-10: 66 - 2026-10-04: 63 - 2026-10-03: 63 - 2026-10-02: 63 - 2026-10-01: 62 - 2026-09-30: 62 ## Common questions ### What is the SELISE Signature MCP server? SELISE Signature is an MCP server listed in the public MCP registry as com.selisesignature/signature. Prepare and send documents for electronic signature with SELISE Signature. This page covers its hosted endpoint (https://signaturemcp.selise.biz/mcp). ### Is the SELISE Signature MCP server safe to use? SELISE Signature scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the SELISE Signature MCP server expose? SELISE Signature exposes 4 tools: prepare_free_signature_document, send_prepared_signature_document, prepare_and_send_free_signature_document, get_signature_document_status. Their descriptions and schemas cost roughly 5,323 tokens of context every time the server is loaded. ### Does the SELISE Signature MCP server require authentication? No. We connected to SELISE Signature without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the SELISE Signature MCP server still maintained? SELISE Signature is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://signaturemcp.selise.biz/mcp - Changelog RSS feed: https://verifymcp.io/servers/com-selisesignature-signature/signaturemcp.xml - Changelog JSON feed: https://verifymcp.io/servers/com-selisesignature-signature/signaturemcp.json - HTML version of this page: https://verifymcp.io/servers/com-selisesignature-signature/signaturemcp