mcp-registry/com.signatureforever/email-signatures · v1.0.0
As of 2026-10-20 16:55 UTC, the Signatureforever Email Signatures MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 26.3 hours.
Audit and build email signatures that survive Gmail, Outlook desktop and Apple Mail.
Claude Code
claude mcp add --transport http signatureforever-email-signatures-mcp-se https://signatureforever.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"signatureforever-email-signatures-mcp-se": {
"type": "http",
"url": "https://signatureforever.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
8 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~2,664 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.signatureforever%2Femail-signatures/fixes
{
"name": "check_email_signature",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"html"
],
"properties": {
"html": {
"type": "string",
"description": "The full HTML of the email signature to audit."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Check an email signature for breakage"
}{
"name": "create_email_signature",
"description": "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.",
"inputSchema": {
"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."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create an email signature"
}{
"name": "get_pricing",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Plans and prices"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.signatureforever/email-signatures"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.signatureforever/email-signatures"}) over MCP.
create_email_signature ~392 tokensemail_client_compatibility_matrix ~177 tokenscheck_email_signature ~170 tokensget_pricing ~87 tokenslist_signature_templates ~61 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.signatureforever%2Femail-signatures?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.signatureforever%2Femail-signatures?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.signatureforever%2Femail-signatures.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.signatureforever%2Femail-signatures.svg :target: https://glimind.com/server/mcp-registry%2Fcom.signatureforever%2Femail-signatures?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d8b9bf792e9cf9c0…, first seen 2026-10-17, included at leaf 3697 of 33,999. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable productivity servers · most reliable knowledge servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 16:55 UTC, the Signatureforever Email Signatures MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 26.3 hours.
Signatureforever Email Signatures MCP server advertises 5 tools, including check_email_signature, create_email_signature, email_client_compatibility_matrix, get_pricing, list_signature_templates.
Point your MCP client at this streamable-http endpoint: https://signatureforever.com/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.