SignaMail
REMOTE · WWW.SIGNAMAIL.FR
Email signatures for French businesses: HTML generator, legal mentions per job, SPF/DKIM/DMARC
Available components
Last scanned (10 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Communication
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 22 Oct 26 +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.
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 71
First indexed and scored.
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 23 Oct 2026 · Probed https://www.signamail.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=signamail.fr | CN=YE1,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 638fa554eb62567af4be3e4daacb868f3da |
| SANs: *.signamail.fr, signamail.fr | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 www.signamail.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | present | 65381 | 13 | Verified |
| signamail.fr. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://*.i.posthog.com https://*.posthog.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://*.i.posthog.com https://*.posthog.com; font-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.signamail.fr/mcp | Verified | 200 | |
| http (plaintext) | http://www.signamail.fr/mcp | HTTPS enforced | 301 | https://www.signamail.fr/mcp |
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 →
check_email_domain Tester SPF, DKIM et DMARC ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain or email address, e.g. mon-entreprise.fr |
No output schema declared.
No examples provided.
generate_email_signature Générer une signature email ~371
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accentColor | string | – | Hex color for the name and links, e.g. #0f766e |
| agendaUrl | string | – | Booking link (Calendly, Google Agenda...) |
| city | string | – | – |
| company | string | – | – |
| string | – | – | |
| string | – | – | |
| firstName | string | yes | 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) |
| string | – | – | |
| jobTitle | string | – | – |
| lastName | string | yes | Last name |
| legalText | string | – | Small print under the signature: legal form, SIRET, regulated mentions |
| 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 | – | – |
| string | – | – | |
| website | string | – | – |
No output schema declared.
No examples provided.
get_install_instructions Installer la signature ~38
Step-by-step instructions (French UI labels) to install an HTML email signature in a given mail client.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
No output schema declared.
No examples provided.
get_profession_signature_rules Mentions obligatoires par métier ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| profession | string | yes | Slug from list_professions, e.g. "avocat" |
No output schema declared.
No examples provided.
get_signamail_plans Offres SignaMail ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_professions Lister les métiers ~59
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · www.signamail.fr
claude mcp add --transport http fr-signamail-signamail 'https://www.signamail.fr/mcp'
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.