SignSimple
REMOTE · SIGNSIMPLE.APP · SCANNED SEP 20
Send PDFs for legally binding e-signature, free and unlimited. Track status; free legal templates.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 485 tokens (~121/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_for_signature" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the SignSimple MCP server?
SignSimple is a hosted endpoint at https://signsimple.app/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.
remote · signsimple.app
claude mcp add --transport http app-signsimple-signsimple 'https://signsimple.app/mcp'
{
"mcpServers": {
"app-signsimple-signsimple": {
"url": "https://signsimple.app/mcp"
}
}
} {
"servers": {
"app-signsimple-signsimple": {
"type": "http",
"url": "https://signsimple.app/mcp"
}
}
} [mcp_servers.app-signsimple-signsimple] url = "https://signsimple.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-signsimple-signsimple": {
"type": "remote",
"url": "https://signsimple.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-signsimple-signsimple --url 'https://signsimple.app/mcp' --transport streamable-http
mcp_servers:
app-signsimple-signsimple:
url: "https://signsimple.app/mcp" {
"McpServers": {
"app-signsimple-signsimple": {
"Transport": "http",
"Url": "https://signsimple.app/mcp"
}
}
} assistant mcp add app-signsimple-signsimple -t streamable-http -u 'https://signsimple.app/mcp'
{
"mcpServers": {
"app-signsimple-signsimple": {
"type": "http",
"url": "https://signsimple.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Sept 26 +1
- Stability: 0.97 → pass security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +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.
- 4 Sept 26 +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.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +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.
- 29 Aug 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://signsimple.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=signsimple.app | CN=YE2,O=Let's Encrypt,C=US | 7 Aug 2026 | 5 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5928e1e3ea3de66f97b4b28557a2bb00a83 |
| SANs: signsimple.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of signsimple.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| signsimple.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://signsimple.app/mcp | Verified | 200 | |
| http (plaintext) | http://signsimple.app/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_document_status ~78
Check the status of a document previously sent for signature: overall state (sent/completed/declined/expired/voided), per-recipient progress (pending/viewed/signed), and the signed PDF download URL once complete. Requires a SignSimple API key.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope_id | string | yes | The envelopeId returned by send_for_signature |
No output schema declared.
No examples provided.
list_documents ~40
List the 25 most recent documents sent from the connected SignSimple account, with status and signed-PDF URLs where complete. Requires a SignSimple API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates ~70
List SignSimple's free, professionally drafted document templates (NDA, lease, contractor agreement, liability waiver, bill of sale, promissory note). Returns each template's info page and direct PDF URL — pass the PDF URL to send_for_signature as document_url to send one. No API key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_for_signature ~224
Send a PDF document for legally binding electronic signature via SignSimple (free, unlimited). Provide the PDF as a fetchable URL or base64, plus recipient name(s) and email(s). Each recipient is emailed a secure signing link; signature and date fields are placed automatically unless custom fields are given. Works with the free templates from list_templates (pass their pdf URL as document_url). Requires a SignSimple API key (create one at https://signsimple.app/profile).
| Name | Type | Req | Description |
|---|---|---|---|
| document_base64 | string | – | Base64-encoded PDF (alternative to document_url) |
| document_name | string | yes | Display name for the document, e.g. "Consulting Agreement.pdf" |
| document_url | string | – | Publicly fetchable URL of the PDF to send |
| expires_in_days | number | – | Days until the signing links expire (optional, default 30) |
| message | string | – | Message included in the signing email (optional) |
| recipients | array | yes | People who must sign, in order |
| subject | string | – | Email subject line (optional) |
No output schema declared.
No examples provided.
What is the SignSimple MCP server?
SignSimple is an MCP server listed in the public MCP registry as app.signsimple/signsimple. Send PDFs for legally binding e-signature, free and unlimited. Track status; free legal templates. This page covers its hosted endpoint (https://signsimple.app/mcp).
Is the SignSimple MCP server safe to use?
SignSimple scores 71 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 SignSimple MCP server expose?
SignSimple exposes 4 tools: send_for_signature, get_document_status, list_documents, list_templates. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.
Does the SignSimple MCP server require authentication?
No. We connected to SignSimple without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SignSimple MCP server still maintained?
SignSimple is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.