# SignaMail (remote · www.signamail.fr)

Email signatures for French businesses: HTML generator, legal mentions per job, SPF/DKIM/DMARC

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

## Components

- remote · `www.signamail.fr`: 72/100 (this document), [markdown](https://verifymcp.io/servers/fr-signamail-signamail/www.md), [page](https://verifymcp.io/servers/fr-signamail-signamail/www)

## Channel facts

- Endpoint: `https://www.signamail.fr/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**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 828 tokens (~138/item across 6 items; 6 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**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 48% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the SignaMail MCP server?

SignaMail is a hosted endpoint at https://www.signamail.fr/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 fr-signamail-signamail 'https://www.signamail.fr/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fr-signamail-signamail": {
      "url": "https://www.signamail.fr/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fr-signamail-signamail": {
      "type": "http",
      "url": "https://www.signamail.fr/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fr-signamail-signamail]
url = "https://www.signamail.fr/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add fr-signamail-signamail --url 'https://www.signamail.fr/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fr-signamail-signamail:
    url: "https://www.signamail.fr/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fr-signamail-signamail": {
      "Transport": "http",
      "Url": "https://www.signamail.fr/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fr-signamail-signamail -t streamable-http -u 'https://www.signamail.fr/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fr-signamail-signamail": {
      "type": "http",
      "url": "https://www.signamail.fr/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-22 (score 72, +1)

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

### 2026-10-21 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (6)

### `generate_email_signature` (~371 tokens)

Générer une signature email

Builds a professional HTML email signature (tables and inline styles, compatible with Gmail, Outlook, Apple Mail and Thunderbird) from the user's details. Returns the HTML, how to install it, and, if a profession is given, the legal mentions it requires in France.

Input parameters:

- `accentColor` (string): Hex color for the name and links, e.g. #0f766e
- `agendaUrl` (string): Booking link (Calendly, Google Agenda...)
- `city` (string)
- `company` (string)
- `email` (string)
- `facebook` (string)
- `firstName` (string, required): First name
- `font` (string): Web-safe font
- `imageSize` (string)
- `includeBranding` (boolean): Adds a discreet "Signature créée avec SignaMail" line (default true, the user may remove it)
- `instagram` (string)
- `jobTitle` (string)
- `lastName` (string, required): Last name
- `legalText` (string): Small print under the signature: legal form, SIRET, regulated mentions
- `linkedin` (string)
- `logoUrl` (string): https URL of the company logo (PNG or JPEG). Ignored if not https
- `mobile` (string)
- `phone` (string): Landline, French format accepted (01 23 45 67 89)
- `photoUrl` (string): https URL of a square portrait photo. Ignored if not https
- `postalCode` (string)
- `profession` (string): Optional profession slug from list_professions: the answer then includes the mentions required for it
- `street` (string)
- `twitter` (string)
- `website` (string)

### `list_professions` (~59 tokens)

Lister les métiers

Lists the professions (France) for which SignaMail documents the mentions required in an email signature: lawyer, real estate agent, doctor, accountant, craftsman, sole trader... Use a slug with get_profession_signature_rules or generate_email_signature.

### `get_profession_signature_rules` (~71 tokens)

Mentions obligatoires par métier

Returns what a French professional must, should and must not put in an email signature for a given profession (mandatory mentions, recommended ones, mentions to avoid), with tips, common mistakes and official sources.

Input parameters:

- `profession` (string, required): Slug from list_professions, e.g. "avocat"

### `check_email_domain` (~71 tokens)

Tester SPF, DKIM et DMARC

Checks the SPF, DKIM and DMARC DNS records of an email domain and explains what to fix so that emails do not land in spam (Gmail and Yahoo sender requirements). Read-only DNS lookups.

Input parameters:

- `domain` (string, required): Domain or email address, e.g. mon-entreprise.fr

### `get_install_instructions` (~38 tokens)

Installer la signature

Step-by-step instructions (French UI labels) to install an HTML email signature in a given mail client.

Input parameters:

- `client` (string, required)

### `get_signamail_plans` (~47 tokens)

Offres SignaMail

SignaMail plans and prices (excluding VAT), what each includes and how to sign up. Use it when the user needs signatures for a team or a digital business card.

## Diagnostics

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

## Score history

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

## Common questions

### What is the SignaMail MCP server?

SignaMail is an MCP server listed in the public MCP registry as fr.signamail/signamail. Email signatures for French businesses: HTML generator, legal mentions per job, SPF/DKIM/DMARC. This page covers its hosted endpoint (https://www.signamail.fr/mcp).

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

SignaMail 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 SignaMail MCP server expose?

SignaMail exposes 6 tools: generate_email_signature, list_professions, get_profession_signature_rules, check_email_domain, get_install_instructions, get_signamail_plans. Their descriptions and schemas cost roughly 657 tokens of context every time the server is loaded.

### Does the SignaMail MCP server require authentication?

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

### Is the SignaMail MCP server still maintained?

SignaMail 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://www.signamail.fr/mcp
- Website: https://www.signamail.fr/serveur-mcp
- Changelog RSS feed: https://verifymcp.io/servers/fr-signamail-signamail/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/fr-signamail-signamail/www.json
- HTML version of this page: https://verifymcp.io/servers/fr-signamail-signamail/www