SignatureForever MCP

A public MCP server that allows agents to audit HTML email signatures for compatibility across major clients, build signatures from templates, retrieve pricing, and access a compatibility matrix. It operates without authentication and uses JSON-RPC 2.0.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by VARGER Group LLC

MCP endpoint (Streamable HTTP)

https://signatureforever.com/mcp

Vendor documentation

What its tools do

5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (5)

check_email_signature
email_client_compatibility_matrix
list_signature_templates
create_email_signature
get_pricing

5 of 5 have a description · 0 of 5 declare behavior hints · 2 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 2:31 PM UTC
Passed Official MCP Registry namespace is tied to signatureforever.com · Nov 6, 2026, 1:58 PM UTC
Passed Endpoint is on the registry namespace domain · Nov 6, 2026, 1:58 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Audit HTML email signatures for client compatibility
Build email-safe HTML signatures from details
List available signature templates
Retrieve current pricing plans

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: com.signatureforever/email-signatures@1.0.0 Project website

Protocol and capabilities

Server: signatureforever 1.0.0
MCP protocol negotiated in check: 2025-06-18
Tools: 5 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

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.

Tools

5 advertised

check_email_signature — Check an email signature for breakage

Advertised by the server during the last successful anonymous check.

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.

check_email_signature input schema

{
  "type": "object",
  "required": [
    "html"
  ],
  "properties": {
    "html": {
      "type": "string",
      "description": "The full HTML of the email signature to audit."
    }
  }
}

email_client_compatibility_matrix — What each email client supports

Advertised by the server during the last successful anonymous check.

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.

email_client_compatibility_matrix 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 — List available signature templates

Advertised by the server during the last successful anonymous check.

The signature layouts you can pass to create_email_signature, with what each one is good for and its width in pixels.

list_signature_templates input schema

{
  "type": "object",
  "properties": {}
}

create_email_signature — Create an email signature

Advertised by the server during the last successful anonymous check.

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.

create_email_signature input schema

{
  "type": "object",
  "required": [
    "full_name"
  ],
  "properties": {
    "city": {
      "type": "string",
      "description": "City, or city and state."
    },
    "email": {
      "type": "string"
    },
    "phone": {
      "type": "string"
    },
    "company": {
      "type": "string"
    },
    "website": {
      "type": "string"
    },
    "language": {
      "enum": [
        "es",
        "en"
      ],
      "type": "string",
      "description": "Language of the credit line. Defaults to 'en'."
    },
    "linkedin": {
      "type": "string"
    },
    "template": {
      "enum": [
        "ficha",
        "cinta",
        "sello",
        "monolinea"
      ],
      "type": "string",
      "description": "Layout. Defaults to 'ficha'. Call list_signature_templates for what each one looks like."
    },
    "whatsapp": {
      "type": "string"
    },
    "full_name": {
      "type": "string",
      "description": "Person's full name. Required."
    },
    "instagram": {
      "type": "string"
    },
    "job_title": {
      "type": "string"
    },
    "photo_url": {
      "type": "string",
      "description": "Absolute https URL of a photo or logo. Anything else is ignored."
    },
    "accent_color": {
      "type": "string",
      "description": "Hex colour like #B4522F. Defaults to the SignatureForever vermilion."
    }
  }
}

get_pricing — Plans and prices

Advertised by the server during the last successful anonymous check.

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.

get_pricing input schema

{
  "type": "object",
  "properties": {}
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

2026-11-06: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 1222 ms
95th percentile latency: 1222 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 2:31 PM UTC · probe · passed · 1222 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add signatureforever-mcp --url https://signatureforever.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable signatureforever-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "signatureforever-mcp": {
      "type": "streamableHttp",
      "url": "https://signatureforever.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start signatureforever-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http signatureforever-mcp https://signatureforever.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://signatureforever.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "signatureforever-mcp": {
      "serverUrl": "https://signatureforever.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like SignatureForever MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

Do you run SignatureForever MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing