# SignatureForever

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

- name: com.signatureforever/email-signatures
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.signatureforever%2Femail-signatures
- tools: https://api.protogrid.dev/v1/servers/com.signatureforever%2Femail-signatures/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "email-signatures": {
      "type": "http",
      "url": "https://signatureforever.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% ~updated-41d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: check_email_signature (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_email_signature (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); email_client_compatibility_matrix (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 747 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 747 tokens to load them all
- tool set hash: 7fdb4d2a68e63f7455dd62111ed6880a
- badge: [![protogrid quality](https://protogrid.dev/badge/com.signatureforever/email-signatures.svg)](https://protogrid.dev/servers/com.signatureforever/email-signatures)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://signatureforever.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## 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.
- `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.
- `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.
- `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.
- `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.