Audits and builds email-signature HTML so it renders correctly across Gmail, Outlook and Apple Mail, and explains SignatureForever plan pricing.
What you can do
The check_email_signature tool audits signature HTML against how Gmail, Outlook 365, Outlook for Windows, Apple Mail and iOS Mail actually render it, returning a per-client verdict plus each problem with the rule broken and a fix. email_client_compatibility_matrix gives a support matrix for HTML and CSS features such as tables, flex/grid, style blocks, background images and web fonts. list_signature_templates lists layouts for create_email_signature, which builds ready-to-paste signature HTML using tables, inline CSS, pixel widths and absolute image URLs. get_pricing describes plan contents and costs.
When to use it
Useful when a signature renders wrong in some mail clients, when you want to check existing signature HTML before sending it out, or when you need to generate a new signature that stays intact in Outlook for Windows and Gmail. Also relevant when a user asks about SignatureForever plan costs or hosted images.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package, environment variables or headers are declared. No authentication is declared.
Before you install
get_pricing covers paid plans and includes a purchase link, so costs and spending may be involved. Signature creation produces HTML intended to be pasted into mail clients, and hosted images are tied to a paid plan. No credentials are requested in the declared configuration.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.signatureforever%2Femail-signatures/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametershtmlrequired
email_client_compatibility_matrix
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.
Parametersfeature
list_signature_templates
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.
Takes no parameters.
create_email_signature
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.
Parameterscityemailphonecompanywebsitelanguagelinkedintemplatewhatsappfull_namerequiredinstagramjob_title+2 more
get_pricing
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.
Takes no parameters.
Version history
1
v1.0.0LatestSep 16, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.