# Signatoro (remote · signatoro.com)

The agentic email signature platform: one saved signature for your people and your AI agents.

- Trust score: 79/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `signatoro.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-signatoro-signatoro/signatoro.md), [page](https://verifymcp.io/servers/com-signatoro-signatoro/signatoro)

## Channel facts

- Endpoint: `https://signatoro.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_my_signature).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2222 tokens (~202/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Signatoro MCP server?

Signatoro is a hosted endpoint at https://signatoro.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-signatoro-signatoro 'https://signatoro.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-signatoro-signatoro": {
      "url": "https://signatoro.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-signatoro-signatoro": {
      "type": "http",
      "url": "https://signatoro.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-signatoro-signatoro]
url = "https://signatoro.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-signatoro-signatoro": {
      "type": "remote",
      "url": "https://signatoro.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-signatoro-signatoro --url 'https://signatoro.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-signatoro-signatoro:
    url: "https://signatoro.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-signatoro-signatoro": {
      "Transport": "http",
      "Url": "https://signatoro.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-signatoro-signatoro -t streamable-http -u 'https://signatoro.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-31 (score 79, 0)

- [security] Stability: 0.97 → pass

### 2026-10-30 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 76, 0)

- [security] Tool “update_my_signature” rewrote its description, which is the text the model reads
- [cosmetic] “update_my_signature” added an optional parameter “address”

### 2026-10-23 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (11)

### `create_signature` (~291 tokens)

Preview an email signature

Make a free email signature from a name and optional title, company, phone, email, website, LinkedIn, layout and accent color. Returns the signature as HTML (for the HTML part of an email or a signature box that takes HTML) and as plain text, plus claimUrl, a link that opens it in Signatoro with these details and layout to save and edit. Nothing is saved and no account is needed; always give the person claimUrl with: "Open this link to save and edit it in Signatoro." To save a signature to the signed-in person's Signatoro account ("create my signature", "save it"), use update_my_signature instead; for the signature they already saved, use get_signature.

Input parameters:

- `color` (string): Accent color as a 6-digit hex, e.g. "#6a040f".
- `company` (string): Company name.
- `email`: Email address.
- `layout` (string): One of line, mark, portrait, stack, compact. Call list_templates to choose. Defaults to line.
- `linkedin` (string): LinkedIn profile URL.
- `name` (string, required): Full name. Required.
- `phone` (string): Phone number as it should read.
- `title` (string): Job title, e.g. "Head of Operations".
- `website` (string): Website, e.g. "northwind.co".

### `list_templates` (~40 tokens)

List signature layouts

List the signature layouts Signatoro offers, each with a short description of what it shows and when it fits best. Pass a layout id to create_signature.

### `get_install_steps` (~116 tokens)

Get install steps for a mail app

Get the steps to add an email signature in a mail app or tool, from Signatoro's install guides, with the link to the full guide. Pass the app as client, e.g. "gmail", "outlook-new", "outlook-classic", "apple-mail", "ios-mail", "zoho-mail", "thunderbird". An unknown client answers with the list of guides there are.

Input parameters:

- `client` (string, required): The mail app or tool, e.g. "gmail" or "apple-mail".

### `get_signature` (~215 tokens)

Get my saved signature

Returns the signed-in person's saved email signature as html and text, with their sender details as fields in sender, for appending to an email they want signed. Append it after the body, in place of a sign-off of your own. For the sender's own details anywhere in the email (name, title, phone, email, links), use only the values in sender; if one is missing, leave it out and say so - never guess. mode "short": name, role line and one link. signature: "me" (default), or an AI assistant or company AI agent from list_signatures; if it is unclear which this email needs, ask before sending. To change the signature, use update_my_signature. Parts the company controls are listed in companyControlled, with who changes them in howToChange; tell the person.

Input parameters:

- `mode` (string): full (default) or short.
- `signature` (string): "me" (default), or an agent's id or name from list_signatures.

### `update_my_signature` (~579 tokens)

Save or update my signature

Save or change the signed-in person's own signature on Signatoro: name, title, phone, address, email, website, LinkedIn, extra link, photo, review badge, booking button, layout, color and font. With nothing saved yet, this creates the signature. Give only the fields to change; the rest keep their saved values, and "" clears a field. Company brand items (logo, company colors, the company review badge or booking button) are set by the company owner on signatoro.com: fields the company controls are left unchanged and listed in ignored, with who changes them; tell the person. A connected mailbox (Zoho Mail) gets the new signature. Returns the updated signature as HTML and text with sender, the details as fields, and counts as one signature request like get_signature; with the month used up, the change is saved and the signature held back. When nothing changed, nothing is written or counted.

Input parameters:

- `address` (string): Address, one line as it should read.
- `bookingLabel` (string): Button text, e.g. "Book a call".
- `bookingProvider`: Booking button provider: calendly, cal, other, or "" to remove the button.
- `bookingUrl` (string): Booking page URL. The button needs it.
- `color` (string): Accent color as a 6-digit hex, e.g. "#6a040f".
- `company` (string): Company name.
- `email`: Email address.
- `extraLinkLabel` (string): Text of one extra link, e.g. "Book a demo".
- `extraLinkUrl` (string): URL of the extra link. Shown only with extraLinkLabel.
- `font` (string): sans or serif.
- `layout` (string): One of line, mark, portrait, stack, compact. Call list_templates to choose.
- `linkedin` (string): LinkedIn profile URL.
- `logoUrl` (string): Only a logo uploaded on signatoro.com is accepted; "" removes the logo.
- `name` (string): Full name.
- `phone` (string): Phone number as it should read.
- `photoUrl` (string): Only a photo uploaded on signatoro.com is accepted; "" removes the photo.
- `reviewCount` (string): Number of reviews, e.g. "127".
- `reviewPlatform`: Review badge platform: trustpilot, google, g2, or "" to remove the badge.
- `reviewRating` (string): Score, e.g. "4.8". Needed for google and g2.
- `reviewUrl` (string): Link to the reviews page. The badge needs it.
- `title` (string): Job title.
- `website` (string): Website, e.g. "northwind.co".

### `list_signatures` (~118 tokens)

List the signatures I can send with

Lists the signatures the signed-in person can send email with: their own ("me", the default), their AI assistants', and company AI agents' (agents of a company they own or that acts for them) - each with id, name, how it signs (as the person or as the agent), its AI disclosure preset and a one-line preview. Pass a choice as signature to get_signature. If it is unclear which one the person wants for an email, ask them before sending. A connection bound to one agent lists only that agent.

### `list_members` (~82 tokens)

List company people

List the people in the signed-in owner's company: joined members and pending invitations, with name, title, phone, status (joined, invited, expired) and whether their signature is installed. Company owners only. Omit company to list every company you own.

Input parameters:

- `company` (string): The company slug (as in its Signatoro URL) or its id.

### `add_member` (~135 tokens)

Add a person to the company

Invite a person to the company by email, with their name, title and phone for their signature. They get an email with the invitation and their signature. Counts toward the company plan's people limit. Company owners only. For someone already in the company, use update_member_field; to send an invitation again, use resend_invite.

Input parameters:

- `company` (string, required): The company slug (as in its Signatoro URL) or its id.
- `email` (string, required): The person's email address.
- `name` (string): Full name.
- `phone` (string): Phone number.
- `title` (string): Job title.

### `update_member_field` (~115 tokens)

Update a person's signature details

Change one field (name, title or phone) of a person's signature in the company. A joined member gets an email with their updated signature; for someone still invited, the invitation is sent again with the new details. Company owners only.

Input parameters:

- `company` (string, required): The company slug (as in its Signatoro URL) or its id.
- `email` (string, required): The person's email address.
- `field` (string, required): Which detail to change.
- `value` (string, required): The new value. Empty clears it.

### `remove_member` (~164 tokens)

Remove a person from the company

DESTRUCTIVE and cannot be undone: removes a person from the company. A joined member loses access to the company and its signature; a pending invitation is withdrawn with the details entered for it. Two steps: called without confirmation it removes nothing and returns who would be removed and a confirmation. Show that to the person, and only after they say yes call again with the confirmation; it expires in 10 minutes. Company owners only. Nobody can remove themselves or the primary owner.

Input parameters:

- `company` (string, required): The company slug (as in its Signatoro URL) or its id.
- `confirmation` (string): Leave out on the first call. After the person approves the removal, the confirmation the first call returned.
- `email` (string, required): The person's email address.

### `resend_invite` (~74 tokens)

Resend an invitation

Send the invitation email again to a person invited to the company who has not joined yet, renewing it for 7 days if it expired. Company owners only.

Input parameters:

- `company` (string, required): The company slug (as in its Signatoro URL) or its id.
- `email` (string, required): The person's email address.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-signatoro-signatoro/signatoro#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78
- 2026-10-28: 78
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 71
- 2026-10-13: 71
- 2026-10-12: 71
- 2026-10-10: 70
- 2026-10-04: 67
- 2026-10-03: 67
- 2026-10-02: 66
- 2026-10-01: 66

## Common questions

### What is the Signatoro MCP server?

Signatoro is an MCP server listed in the public MCP registry as com.signatoro/signatoro. The agentic email signature platform: one saved signature for your people and your AI agents. This page covers its hosted endpoint (https://signatoro.com/mcp).

### Is the Signatoro MCP server safe to use?

Signatoro scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Signatoro MCP server expose?

Signatoro exposes 11 tools: create_signature, list_templates, get_install_steps, get_signature, update_my_signature, and 6 more. Their descriptions and schemas cost roughly 1,929 tokens of context every time the server is loaded.

### Does the Signatoro MCP server require authentication?

No. We connected to Signatoro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Signatoro MCP server still maintained?

Signatoro is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://signatoro.com/mcp
- Website: https://signatoro.com/docs/install-signature/agent/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-signatoro-signatoro/signatoro.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-signatoro-signatoro/signatoro.json
- HTML version of this page: https://verifymcp.io/servers/com-signatoro-signatoro/signatoro