# ProSignature email signatures (remote · prosignature.co)

Build free email signatures, quote Pro and Teams prices, get install steps. Read-only, no account.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `prosignature.co`: 72/100 (this document), [markdown](https://verifymcp.io/servers/co-prosignature-email-signatures/prosignature.md), [page](https://verifymcp.io/servers/co-prosignature-email-signatures/prosignature)

## Channel facts

- Endpoint: `https://prosignature.co/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-10-23.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 767 tokens (~153/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the ProSignature email signatures MCP server?

ProSignature email signatures is a hosted endpoint at https://prosignature.co/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 co-prosignature-email-signatures 'https://prosignature.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-prosignature-email-signatures": {
      "url": "https://prosignature.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-prosignature-email-signatures": {
      "type": "http",
      "url": "https://prosignature.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-prosignature-email-signatures]
url = "https://prosignature.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-prosignature-email-signatures": {
      "type": "remote",
      "url": "https://prosignature.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-prosignature-email-signatures --url 'https://prosignature.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-prosignature-email-signatures:
    url: "https://prosignature.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-prosignature-email-signatures": {
      "Transport": "http",
      "Url": "https://prosignature.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-prosignature-email-signatures -t streamable-http -u 'https://prosignature.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-prosignature-email-signatures": {
      "type": "http",
      "url": "https://prosignature.co/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-23 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-20 (score 70)

First indexed and scored.

## MCP tools (5)

### `create_signature` (~268 tokens)

Create an email signature (free, no account)

Builds the email-safe HTML signature (table + inline styles, the same bytes as prosignature.co/email-signature-generator) for one person. Returns html, a plain-text version, an edit_url that opens the generator prefilled, and install steps for Gmail, Outlook and Apple Mail. The output is the free plan: four layouts, six accent colours, no logo or photo, and a small clickable "Created with ProSignature" credit line under the signature (Pro removes it). Nothing is installed or stored.

Input parameters:

- `colour` (string): Accent colour #rrggbb (default #E8604C); the page offers #E8604C, #2B6CB0, #2F855A, #6B46C1, #2B2620, #B7791F
- `company` (string): Company or business name
- `email` (string): Email address
- `layout` (string): Layout id (default classic)
- `name` (string, required): Full name (required)
- `phone` (string): Phone, as it should read; the tel: link keeps digits and +
- `title` (string): Job title
- `website` (string): Website: bare domain (https:// is added) or an http(s) URL

### `list_layouts` (~32 tokens)

List layouts and colours

The four signature layouts (id, name, what it looks like) and the six accent colours the generator offers.

### `quote_price` (~151 tokens)

Quote a ProSignature price

List price for Pro (one person) or Teams (per person, 5-person minimum, no platform fee) for a number of people, billed yearly or monthly, computed from the rules in https://prosignature.co/pricing.json (verified 2026-10-18). The admin counts as one of the people. Free plan: $0, credit line. This is a quote, not a checkout: the human pays in the app after signing up.

Input parameters:

- `billing` (string): Billing period (default yearly)
- `people` (integer): How many people, admin included (default 1)
- `plan` (string, required): pro = one person; teams = a company (admin + employees)

### `get_install_steps` (~92 tokens)

Install steps for a mail client

How a signature from create_signature gets into a mail client, honestly: Gmail web (paste, or the sendAs PATCH with gmail.settings.basic — new mail only), Gmail mobile, Outlook (copy-paste only, no directory sync), Apple Mail, iPhone. The free Chrome extension (auto-updates, covers replies) needs the human to sign up first.

Input parameters:

- `client` (string, required): Which mail client

### `get_facts` (~83 tokens)

ProSignature facts

What ProSignature is, the free plan and its credit line, Pro and Teams prices (verified 2026-10-18), how Gmail and Google Workspace installs work per person, personal links for employees, what the product is NOT (no mail-flow enforcement, no Microsoft 365 sync, no analytics), and where the docs, OpenAPI and pricing.json are.

## Diagnostics

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

## Score history

- 2026-10-23: 72
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 70

## Common questions

### What is the ProSignature email signatures MCP server?

ProSignature email signatures is an MCP server listed in the public MCP registry as co.prosignature/email-signatures. Build free email signatures, quote Pro and Teams prices, get install steps. Read-only, no account. This page covers its hosted endpoint (https://prosignature.co/mcp).

### Is the ProSignature email signatures MCP server safe to use?

ProSignature email signatures scores 72 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 ProSignature email signatures MCP server expose?

ProSignature email signatures exposes 5 tools: create_signature, list_layouts, quote_price, get_install_steps, get_facts. Their descriptions and schemas cost roughly 626 tokens of context every time the server is loaded.

### Does the ProSignature email signatures MCP server require authentication?

No. We connected to ProSignature email signatures without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ProSignature email signatures MCP server still maintained?

ProSignature email signatures is still listed as active in the MCP registry. We last reached this channel on 23 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://prosignature.co/mcp
- Website: https://prosignature.co/for-ai-agents
- Changelog RSS feed: https://verifymcp.io/servers/co-prosignature-email-signatures/prosignature.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-prosignature-email-signatures/prosignature.json
- HTML version of this page: https://verifymcp.io/servers/co-prosignature-email-signatures/prosignature