Skip to content

SignatureForever

by signatureforever.com · remote · no sign-in to list tools · v1.0.0 · published by com.signatureforever

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

Changes · 3
CompareRegistry entry

5 tools: 3 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http email-signatures https://signatureforever.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 3Claude Code: ask
  • check_email_signatureAudit any email-signature HTML against what Gmail, Outlook 365, Outlook for Windows desktop, Apple Mail and iOS Mail actually do.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • create_email_signatureBuild ready-to-paste email-signature HTML from a person's details.No findings

    Why it is in this group

    • The name "create_email_signature" says "create": a word for a change.
    Description, as the server wrote it
    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.
  • email_client_compatibility_matrixThe 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,…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 2Claude Code: allow
  • get_pricingWhat each SignatureForever plan includes and costs, and the link to buy.No findings

    Why it is in this group

    • The name "get_pricing" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_signature_templatesThe signature layouts you can pass to create_email_signature, with what each one is good for and its width in pixels.No findings

    Why it is in this group

    • The name "list_signature_templates" says "list": a word for reading.
    Description, as the server wrote it
    The signature layouts you can pass to create_email_signature, with what each one is good for and its width in pixels.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http email-signatures https://signatureforever.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__email-signatures__list_signature_templates",
      "mcp__email-signatures__get_pricing"
    ],
    "ask": [
      "mcp__email-signatures__check_email_signature",
      "mcp__email-signatures__email_client_compatibility_matrix",
      "mcp__email-signatures__create_email_signature"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as email-signatures. Review it before you use it.