Content Tools

signatureforever.com

Generates and audits email-signature HTML for compatibility across major email clients, with templates and plan pricing.

1 endpoint5 known toolsFirst detected September 10, 2026Last detected September 10, 2026

ENDPOINT 1

https://signatureforever.com/mcp

No auth detected

MCP server metadata

Name: signatureforever
Version: 1.0.0

Capabilities

tools

Server instructions

SignatureForever builds email signatures that survive real email clients, and audits ones you already have. Start with check_email_signature when the user already has a signature and something looks broken: it names the exact rule, the clients it breaks in, and the fix. Use email_client_compatibility_matrix when you need to answer what a given email client supports. Use create_email_signature to produce ready-to-paste HTML. Free signatures carry one small credit line at the bottom; get_pricing explains how to remove it and what else the paid tiers include.

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

Potential side effects

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.

Potential side effects

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.

Inferred read-only

create_email_signature

Build ready-to-paste email-signature HTML from a person's details.

Potential side effects

get_pricing

What each SignatureForever plan includes and costs, and the link to buy.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.signatureforever]
url = "https://signatureforever.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "signatureforever": {
      "type": "http",
      "url": "https://signatureforever.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: signatureforever
Remote MCP URL: https://signatureforever.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "signatureforever": {
      "url": "https://signatureforever.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "signatureforever": {
      "type": "http",
      "url": "https://signatureforever.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

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

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.