SignatureForever
Audit and build email signatures that survive Gmail, Outlook desktop and Apple Mail.
Should I use this
Quality & Safety
Findings (1)
- LOWTool 'email_client_compatibility_matrix' name length outside 3-30 rangein email_client_compatibility_matrix
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"email-signatures": {
"url": "https://signatureforever.com/mcp"
}
}
}Remote endpoints
https://signatureforever.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (5)
🟢check_email_signature(html)
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 Schema
{
"type": "object",
"properties": {
"html": {
"type": "string",
"description": "The full HTML of the email signature to audit."
}
},
"required": [
"html"
]
}⚪email_client_compatibility_matrix(feature)
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 Schema
{
"type": "object",
"properties": {
"feature": {
"type": "string",
"description": "Optional. Filter to rows whose feature name contains this text, e.g. 'base64' or 'font'."
}
}
}🟡list_signature_templates
The signature layouts you can pass to create_email_signature, with what each one is good for and its width in pixels.
Input Schema
{
"type": "object",
"properties": {}
}🔴create_email_signature(full_name, job_title, company, email, phone, ...)
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 Schema
{
"type": "object",
"properties": {
"full_name": {
"type": "string",
"description": "Person's full name. Required."
},
"job_title": {
"type": "string"
},
"company": {
"type": "string"
},
"email": {
"type": "string"
},
"phone": {
"type": "string"
},
"website": {
"type": "string"
},
"city": {
"type": "string",
"description": "City, or city and state."
},
"photo_url": {
"type": "string",
"description": "Absolute https URL of a photo or logo. Anything else is ignored."
},
"linkedin": {
"type": "string"
},
"instagram": {
"type": "string"
},
"whatsapp": {
"type": "string"
},
"template": {
"type": "string",
"enum": [
"ficha",
"cinta",
"sello",
"monolinea"
],
"description": "Layout. Defaults to 'ficha'. Call list_signature_templates for what each one looks like."
},
"accent_color": {
"type": "string",
"description": "Hex colour like #B4522F. Defaults to the SignatureForever vermilion."
},
"language": {
"type": "string",
"enum": [
"es",
"en"
],
"description": "Language of the credit line. Defaults to 'en'."
}
},
"required": [
"full_name"
]
}🟢get_pricing
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.
Input Schema
{
"type": "object",
"properties": {}
}Community
Evidence