Signatoro
REMOTE · SIGNATORO.COM
The agentic email signature platform: one saved signature for your people and your AI agents.
Available components
Last scanned (2 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_my_signature). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 0
- Tool “update_my_signature” rewrote its description, which is the text the model reads security
- “update_my_signature” added an optional parameter “address” cosmetic
- 23 Oct 26 +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.
- 21 Oct 26 +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.
- 19 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://signatoro.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.signatoro.com | CN=YR2,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 60f951846f8cfc293fc63b362f7e2f73661 |
| SANs: *.signatoro.com, signatoro.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of signatoro.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| signatoro.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://signatoro.com/mcp | Verified | 200 | |
| http (plaintext) | http://signatoro.com/mcp | HTTPS enforced | 308 | https://signatoro.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_member Add a person to the company ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | The company slug (as in its Signatoro URL) or its id. |
| string | yes | The person's email address. | |
| name | string | – | Full name. |
| phone | string | – | Phone number. |
| title | string | – | Job title. |
No output schema declared.
No examples provided.
create_signature Preview an email signature ~291
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.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Accent color as a 6-digit hex, e.g. "#6a040f". |
| company | string | – | Company name. |
| – | – | Email address. | |
| layout | string | – | One of line, mark, portrait, stack, compact. Call list_templates to choose. Defaults to line. |
| string | – | LinkedIn profile URL. | |
| name | string | yes | 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". |
No output schema declared.
No examples provided.
get_install_steps Get install steps for a mail app ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | The mail app or tool, e.g. "gmail" or "apple-mail". |
No output schema declared.
No examples provided.
get_signature Get my saved signature ~215
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | full (default) or short. |
| signature | string | – | "me" (default), or an agent's id or name from list_signatures. |
No output schema declared.
No examples provided.
list_members List company people ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The company slug (as in its Signatoro URL) or its id. |
No output schema declared.
No examples provided.
list_signatures List the signatures I can send with ~118
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates List signature layouts ~40
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remove_member Remove a person from the company ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | 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. |
| string | yes | The person's email address. |
No output schema declared.
No examples provided.
resend_invite Resend an invitation ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | The company slug (as in its Signatoro URL) or its id. |
| string | yes | The person's email address. |
No output schema declared.
No examples provided.
update_member_field Update a person's signature details ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | The company slug (as in its Signatoro URL) or its id. |
| string | yes | The person's email address. | |
| field | string | yes | Which detail to change. |
| value | string | yes | The new value. Empty clears it. |
No output schema declared.
No examples provided.
update_my_signature Save or update my signature ~579
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 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. |
| 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". |
No output schema declared.
No examples provided.
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.
remote · signatoro.com
claude mcp add --transport http com-signatoro-signatoro 'https://signatoro.com/mcp'
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.