# SignSimple (remote · signsimple.app)

Send PDFs for legally binding e-signature, free and unlimited. Track status; free legal templates.

- Trust score: 71/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `signsimple.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/app-signsimple-signsimple/signsimple.md), [page](https://verifymcp.io/servers/app-signsimple-signsimple/signsimple)

## Channel facts

- Endpoint: `https://signsimple.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 485 tokens (~121/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http app-signsimple-signsimple 'https://signsimple.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-signsimple-signsimple": {
      "url": "https://signsimple.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-signsimple-signsimple": {
      "type": "http",
      "url": "https://signsimple.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-signsimple-signsimple]
url = "https://signsimple.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-signsimple-signsimple": {
      "type": "remote",
      "url": "https://signsimple.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-signsimple-signsimple --url 'https://signsimple.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-signsimple-signsimple:
    url: "https://signsimple.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-signsimple-signsimple": {
      "Transport": "http",
      "Url": "https://signsimple.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-signsimple-signsimple -t streamable-http -u 'https://signsimple.app/mcp'
```

### Other

```json
{
  "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.

## 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-09-13 (score 71, +1)

- [security] Stability: 0.97 → pass

### 2026-09-11 (score 70, +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.

### 2026-09-09 (score 69, +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.

### 2026-09-06 (score 68, +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-09-04 (score 67, +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-09-02 (score 66, +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.

### 2026-08-31 (score 65, +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-08-29 (score 64, +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.

## MCP tools (4)

### `send_for_signature` (~224 tokens)

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).

Input parameters:

- `document_base64` (string): Base64-encoded PDF (alternative to document_url)
- `document_name` (string, required): 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, required): People who must sign, in order
- `subject` (string): Email subject line (optional)

### `get_document_status` (~78 tokens)

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.

Input parameters:

- `envelope_id` (string, required): The envelopeId returned by send_for_signature

### `list_documents` (~40 tokens)

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.

### `list_templates` (~70 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-signsimple-signsimple/signsimple#diagnostics

## Score history

- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 71
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 68
- 2026-09-05: 67
- 2026-09-04: 67
- 2026-09-03: 66
- 2026-09-02: 66
- 2026-09-01: 65
- 2026-08-31: 65
- 2026-08-30: 64
- 2026-08-29: 64
- 2026-08-28: 63
- 2026-08-27: 63
- 2026-08-26: 62
- 2026-08-25: 62
- 2026-08-24: 61
- 2026-08-23: 61
- 2026-08-22: 60

## Common questions

### 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.

## Links

- Remote endpoint: https://signsimple.app/mcp
- Website: https://signsimple.app/developers
- Changelog RSS feed: https://verifymcp.io/servers/app-signsimple-signsimple/signsimple.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-signsimple-signsimple/signsimple.json
- HTML version of this page: https://verifymcp.io/servers/app-signsimple-signsimple/signsimple