Skip to content

Signatoro MCP server

com.signatoro/signatorosignatoro.comstreamable-httpv1.0.1Scanned

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

11 tools: 3 can delete or cancel things, 2 do something that can't be undone, 1 change things and 5 only read.

Tools: 3 delete, 2 irreversible, 1 write, 5 read.
  • Reads private data · 3
  • Reads text others write · 7
  • Can send data out · 3
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things and 2 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Signatoro MCP server can do

The Signatoro MCP server is published by signatoro.com, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (3 tools: update_my_signature, update_member_field and remove_member), do things that cannot be undone, such as sending, paying or publishing (add_member and resend_invite) and create or change data (1 tool: create_signature). 5 tools only read.

3 tools read private data (get_install_steps, get_signature and list_signatures); 7 tools bring in text other people can write (get_install_steps, get_signature, update_my_signature and 4 more); 3 tools can send data out of your system (create_signature, add_member and resend_invite). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Deletes or cancels 3Claude Code: deny
  • remove_memberDESTRUCTIVE and cannot be undone: removes a person from the company.No findings

    Why it is in this group

    • The name "remove_member" says "remove": a word for removing or ending something.
    • The description says "cannot be undone".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Remove a person from the company
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • update_member_fieldChange one field (name, title or phone) of a person's signature in the company.Reads text others writeNo findings

    Why it is in this group

    • The name "update_member_field" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update a person's signature details
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • update_my_signatureSave 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, co…Reads text others writeNo findings

    Why it is in this group

    • The name "update_my_signature" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Save or update my signature
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Can't be undone 2Claude Code: ask
  • add_memberInvite a person to the company by email, with their name, title and phone for their signature.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "add_member" says "add": a word for a change.
    • The description's first verb is "invite": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Add a person to the company
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • resend_inviteSend the invitation email again to a person invited to the company who has not joined yet, renewing it for 7 days if it expired.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "resend_invite" says "resend": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "resend_invite" says "resend": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Resend an invitation
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 1Claude Code: ask
  • create_signatureMake a free email signature from a name and optional title, company, phone, email, website, LinkedIn, layout and accent color.Can send data out1 finding

    Why it is in this group

    • The name "create_signature" says "create": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.

    Findings

    • Warn

      The server marks "create_signature" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_signature" says "create": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Preview an email signature
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • get_install_stepsGet 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.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_install_steps" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get install steps for a mail app
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_signatureReturns 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.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_signature" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "return" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get my saved signature
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • list_membersList 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 …No findings

    Why it is in this group

    • The name "list_members" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List company people
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_signaturesLists 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 act…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_signatures" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List the signatures I can send with
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_templatesList the signature layouts Signatoro offers, each with a short description of what it shows and when it fits best.No findings

    Why it is in this group

    • The name "list_templates" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List signature layouts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

63 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 3 outbound tools breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__signatoro__add_member",
      "mcp__signatoro__create_signature",
      "mcp__signatoro__resend_invite"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:47 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://signatoro.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://signatoro.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (3 destructive, 2 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://signatoro.com/mcp: tools/list returned 11 tools to an anonymous client, including update_my_signature (destructive), update_member_field (destructive), remove_member (destructive), add_member (irreversible), resend_invite (irreversible) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "create_signature" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_signature" says "create": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__signatoro__list_templates",
      "mcp__signatoro__get_install_steps",
      "mcp__signatoro__get_signature",
      "mcp__signatoro__list_signatures",
      "mcp__signatoro__list_members"
    ],
    "ask": [
      "mcp__signatoro__create_signature",
      "mcp__signatoro__add_member",
      "mcp__signatoro__resend_invite"
    ],
    "deny": [
      "mcp__signatoro__update_my_signature",
      "mcp__signatoro__update_member_field",
      "mcp__signatoro__remove_member"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as signatoro. Review it before you use it.

Capability tags behind 8 rules
  • mcp__signatoro__create_signature outbound
  • mcp__signatoro__get_install_steps private-data, untrusted-input
  • mcp__signatoro__get_signature private-data, untrusted-input
  • mcp__signatoro__update_my_signature untrusted-input
  • mcp__signatoro__list_signatures private-data, untrusted-input
  • mcp__signatoro__add_member untrusted-input, outbound
  • mcp__signatoro__update_member_field untrusted-input
  • mcp__signatoro__resend_invite untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.signatoro/signatoro/verify?hash=c002ee3b6f47e7e11945587026d3ecdcc04eea7f1e703ee24ea19fc16b398c09" | jq -e '.changed == false'

Pinned hash c002ee3b6f47, from Nov 14, 2026, 08:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.signatoro/signatoro/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.signatoro/signatoro
[![Anlyon Radar](https://radar.anlyon.com/badge/com.signatoro/signatoro.svg)](https://radar.anlyon.com/servers/com.signatoro/signatoro)

Source: MCP Registry. Synced Oct 21, 2026, 18:04 UTC.

Signatoro MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Signatoro MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Signatoro MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: update_my_signature, update_member_field and remove_member.

Can the Signatoro MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: add_member and resend_invite.

What tools does the Signatoro MCP server have?

11 tools: 3 destructive, 2 irreversible, 1 write, 5 read. update_my_signature, update_member_field, remove_member, add_member, resend_invite, create_signature, list_templates, get_install_steps and 3 more.

Does the Signatoro MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Signatoro MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_signature, add_member and resend_invite.

Has the Signatoro MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 1, 2026. Every change is on this page and in its Atom feed.