# SignatureForever (remote · signatureforever.com)

Audit and build email signatures that survive Gmail, Outlook desktop and Apple Mail.

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

## Components

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

## Channel facts

- Endpoint: `https://signatureforever.com/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**: 63/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 5 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 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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 699 tokens (~139/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**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% 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 SignatureForever MCP server?

SignatureForever is a hosted endpoint at https://signatureforever.com/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-signatureforever-email-signatures 'https://signatureforever.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-signatureforever-email-signatures": {
      "url": "https://signatureforever.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-signatureforever-email-signatures:
    url: "https://signatureforever.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-signatureforever-email-signatures": {
      "type": "http",
      "url": "https://signatureforever.com/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-20 (score 69, +1)

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

### 2026-09-18 (score 68, +48)

- [security improvement] HTTPS: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.27

### 2026-09-17 (score 20, −47)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-16 (score 67, +1)

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

### 2026-09-13 (score 66, +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-09-11 (score 65, −1)

- [functional regression] MCP protocol: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] MCP protocol version: 2026-07-28 → 2025-06-18

### 2026-09-10 (score 66)

First indexed and scored.

## MCP tools (5)

### `check_email_signature` (~114 tokens)

Check an email signature for breakage

Audit any email-signature HTML against what Gmail, Outlook 365, Outlook for Windows desktop, Apple Mail and iOS Mail actually do. Returns a verdict per client plus every problem found, each with the rule it breaks, why it breaks, and how to fix it. Use this when a signature renders wrong, images do not show, layout collapses in Outlook, or before sending a signature to a client. Free, no account needed.

Input parameters:

- `html` (string, required): The full HTML of the email signature to audit.

### `email_client_compatibility_matrix` (~122 tokens)

What each email client supports

The support matrix for the HTML and CSS features that decide whether an email signature survives: tables, flex/grid, <style> blocks, background-image, base64 images, border-radius, letter-spacing, text-transform, web fonts, max-width, margins and image sizing. Each row says yes/no/partial for seven real clients and explains what goes wrong. Use it to answer questions about email HTML support.

Input parameters:

- `feature` (string): Optional. Filter to rows whose feature name contains this text, e.g. 'base64' or 'font'.

### `list_signature_templates` (~33 tokens)

List available signature templates

The signature layouts you can pass to create_email_signature, with what each one is good for and its width in pixels.

### `create_email_signature` (~263 tokens)

Create an email signature

Build ready-to-paste email-signature HTML from a person's details. The output follows every rule that keeps a signature intact in Outlook for Windows and Gmail: tables only, inline CSS, absolute pixel widths, email-safe fonts, and images by absolute URL (never base64, which Gmail refuses to render). The free result carries one small credit line at the bottom; get_pricing explains how to remove it.

Input parameters:

- `accent_color` (string): Hex colour like #B4522F. Defaults to the SignatureForever vermilion.
- `city` (string): City, or city and state.
- `company` (string)
- `email` (string)
- `full_name` (string, required): Person's full name. Required.
- `instagram` (string)
- `job_title` (string)
- `language` (string): Language of the credit line. Defaults to 'en'.
- `linkedin` (string)
- `phone` (string)
- `photo_url` (string): Absolute https URL of a photo or logo. Anything else is ignored.
- `template` (string): Layout. Defaults to 'ficha'. Call list_signature_templates for what each one looks like.
- `website` (string)
- `whatsapp` (string)

### `get_pricing` (~55 tokens)

Plans and prices

What each SignatureForever plan includes and costs, and the link to buy. Use it when the user asks what removing the credit line costs, how many signatures a plan allows, or what happens to hosted images if they stop paying.

## Diagnostics

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

## Score history

- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 20
- 2026-09-16: 67
- 2026-09-15: 66
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 66

## Common questions

### What is the SignatureForever MCP server?

SignatureForever is an MCP server listed in the public MCP registry as com.signatureforever/email-signatures. Audit and build email signatures that survive Gmail, Outlook desktop and Apple Mail. This page covers its hosted endpoint (https://signatureforever.com/mcp).

### Is the SignatureForever MCP server safe to use?

SignatureForever scores 69 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 SignatureForever MCP server expose?

SignatureForever exposes 5 tools: check_email_signature, email_client_compatibility_matrix, list_signature_templates, create_email_signature, get_pricing. Their descriptions and schemas cost roughly 587 tokens of context every time the server is loaded.

### Does the SignatureForever MCP server require authentication?

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

### Is the SignatureForever MCP server still maintained?

SignatureForever 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://signatureforever.com/mcp
- Website: https://signatureforever.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-signatureforever-email-signatures/signatureforever.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-signatureforever-email-signatures/signatureforever.json
- HTML version of this page: https://verifymcp.io/servers/com-signatureforever-email-signatures/signatureforever