SignatureForever

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

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

Measured statistics

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "SignatureForever": {
      "url": "https://signatureforever.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (5)

• check_email_signature

  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.

  Parameters:

  • html (required) — string — The full HTML of the email signature to audit.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• email_client_compatibility_matrix

  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.

  Parameters:

  • feature — string — Optional. Filter to rows whose feature name contains this text, e.g. 'base64' or 'font'.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• create_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.

  Parameters:

  • full_name (required) — string — Person's full name. Required.
  • city — string — City, or city and state.
  • email — string
  • phone — string
  • company — string
  • website — string
  • language — string — Language of the credit line. Defaults to 'en'.
  • linkedin — string
  • template — string — Layout. Defaults to 'ficha'. Call list_signature_templates for what each one looks like.
  • whatsapp — string
  • instagram — string
  • job_title — string
  • photo_url — string — Absolute https URL of a photo or logo. Anything else is ignored.
  • accent_color — string — Hex colour like #B4522F. Defaults to the SignatureForever vermilion.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.