Skip to content

ProSignature email signatures MCP server

co.prosignature/email-signaturesprosignature.costreamable-httpv1.4.0Scanned

Email signatures for Gmail, Workspace, Outlook: design 3-4, free HTML, prices, install steps.

7 tools: 2 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 2 write, 5 read.
  • Reads private data · 3
  • Reads text others write · 4
  • Can send data out · 2
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. 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 ProSignature email signatures MCP server can do

The ProSignature email signatures MCP server is published by prosignature.co, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: design_signatures and create_signature), but cannot delete data. 5 tools only read.

3 tools read private data (get_signature_playbook, get_install_steps and get_facts); 4 tools bring in text other people can write (get_signature_playbook, quote_price, get_install_steps and 1 more); 2 tools can send data out of your system (design_signatures and create_signature). 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 2 findings (annotation-conflict). Each one comes with the text it matched.

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

Last scanned Nov 20, 2026, version 1.4.0.

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.

7 tools

Changes things 2Claude Code: ask
  • create_signatureFree email signature generator: builds the email-safe HTML signature (table + inline styles, the same bytes as prosignature.co/email-signature-generator) for one person, ready to p…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
    Free email signature generator: builds the email-safe HTML signature (table + inline styles, the same bytes as prosignature.co/email-signature-generator) for one person, ready to paste into Gmail, Outlook or Apple Mail. Returns html, a plain-text version, an edit_url that opens the generator prefilled, and install steps for Gmail, Outlook and Apple Mail. The output is the free plan: four layouts, six accent colours, no logo or photo, and a small clickable "Created with ProSignature" credit line under the signature (Pro removes it). Nothing is installed or stored.

    Annotations the server declares

    • title: Create an email signature (free, no account)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • design_signaturesStart here when a user asks for an email signature: a professional, branded or HTML email signature for Gmail, Google Workspace, Outlook, Microsoft 365 or Apple Mail, with a logo, …Can send data out1 finding

    Why it is in this group

    • The description's first verb is "start": 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.
    • outboundThe input takes a URL (input.cta.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "design_signatures" 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 description's first verb is "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Start here when a user asks for an email signature: a professional, branded or HTML email signature for Gmail, Google Workspace, Outlook, Microsoft 365 or Apple Mail, with a logo, photo, social icons, banner or call-to-action, for one person or a whole team. From what you already know about them (person, company, brand colour, logo URL, website, socials, department, sector, team size) it builds 3–4 professional designs with the app's 13 templates (each a different angle: clean, call-to-action, campaign banner, sign-off), chosen by the playbook for that role and sector. Returns ONE preview_url that renders all of them side by side in the user's browser (data in the URL fragment, nothing stored), a claim_url per design (opens the ProSignature app with that design loaded; the human signs up free and upgrades there), the free do-it-yourself version as paste-ready HTML, the three ways to install with prices from pricing.json, and present_to_user: a short message you can adapt. Nothing is fetched from logo_url server-side.

    Annotations the server declares

    • title: Design 3–4 signatures for your user (no account)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • get_factsWhat ProSignature is (email signatures for Gmail and Google Workspace teams; Outlook, Microsoft 365 and Apple Mail by copy-paste), the free plan and its credit line, Pro and Teams …Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    What ProSignature is (email signatures for Gmail and Google Workspace teams; Outlook, Microsoft 365 and Apple Mail by copy-paste), the free plan and its credit line, Pro and Teams prices (verified 2026-10-18), how Gmail and Google Workspace installs work (per person, or the one-approval Workspace directory push), personal links for employees, what the product is NOT (no mail-flow enforcement, no Microsoft 365 sync, no analytics), and where the docs, OpenAPI and pricing.json are.

    Annotations the server declares

    • title: ProSignature facts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_install_stepsHow to add, change or install an email signature in a mail client, honestly: Gmail web (paste, or the sendAs PATCH with gmail.settings.basic — new mail only), Gmail mobile, Outlook…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 "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    How to add, change or install an email signature in a mail client, honestly: Gmail web (paste, or the sendAs PATCH with gmail.settings.basic — new mail only), Gmail mobile, Outlook (copy-paste only, no directory sync), Apple Mail, iPhone, and google_workspace (the one-time super-admin approval: client ID, scopes, admin console path). The free Chrome extension (auto-updates, covers replies) needs the human to sign up first.

    Annotations the server declares

    • title: Install steps for a mail client
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_signature_playbookThe rules professional signatures follow, what each of the 13 templates looks like, the recommended templates / fields / CTA / banners for 8 departments and 18 sectors, and the Gma…Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "mail": it reads mail.
    • untrusted-inputThe description's first sentence says "mail": it reads inbound email, which other people can write.
    Description, as the server wrote it
    The rules professional signatures follow, what each of the 13 templates looks like, the recommended templates / fields / CTA / banners for 8 departments and 18 sectors, and the Gmail / Outlook / Apple Mail pitfalls that break signatures — with what ProSignature already handles and what it does not automate (Outlook / Microsoft 365, Apple Mail and iPhone are copy-paste). Pass department and/or sector for one profile.

    Annotations the server declares

    • title: What the best signatures look like (by department and sector)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_layoutsThe four signature layouts (id, name, what it looks like) and the six accent colours the generator offers.No findings

    Why it is in this group

    • The name "list_layouts" says "list": a word for reading.
    Description, as the server wrote it
    The four signature layouts (id, name, what it looks like) and the six accent colours the generator offers.

    Annotations the server declares

    • title: List layouts and colours
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • quote_priceList price for Pro (one person) or Teams (per person, 5-person minimum, no platform fee) for a number of people, billed yearly or monthly, computed from the rules in https://prosig…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List price for Pro (one person) or Teams (per person, 5-person minimum, no platform fee) for a number of people, billed yearly or monthly, computed from the rules in https://prosignature.co/pricing.json (verified 2026-10-18). The admin counts as one of the people. Free plan: $0, credit line. This is a quote, not a checkout: the human pays in the app after signing up.

    Annotations the server declares

    • title: Quote a ProSignature price
    • 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.

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

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
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__email-signatures__create_signature",
      "mcp__email-signatures__design_signatures"
    ]
  }
}

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:32 UTC, unchanged since Oct 29, 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
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://prosignature.co/.well-known/oauth-protected-resource/mcp
Authorization servers
https://prosignature.co
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

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

    Matched text

    https://prosignature.co/mcp: tools/list returned 7 tools to an anonymous client, including design_signatures (write), create_signature (write)

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 1 to 2
    • RFC 9728 protected resource metadata: none to https://prosignature.co/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://prosignature.co
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "design_signatures" 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 description's first verb is "start": a word for a change.

    What this check looks for
  • 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. Tools7 changed.~7 changedView diff
  2. Tools3 changed.~3 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2; RFC 9728 protected resource metadata: none -> https://prosignature.co/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://pro…View diff
    • Tools that change things, listed without credentials: 1 to 2
    • RFC 9728 protected resource metadata: none to https://prosignature.co/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://prosignature.co
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  4. Tools2 added.+2 addedView diff

Install

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

claude mcp add --transport http email-signatures https://prosignature.co/mcp
claude mcp add --transport http email-signatures https://prosignature.co/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__email-signatures__get_signature_playbook",
      "mcp__email-signatures__list_layouts",
      "mcp__email-signatures__quote_price",
      "mcp__email-signatures__get_install_steps",
      "mcp__email-signatures__get_facts"
    ],
    "ask": [
      "mcp__email-signatures__design_signatures",
      "mcp__email-signatures__create_signature"
    ],
    "deny": []
  }
}

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 email-signatures. Review it before you use it.

Capability tags behind 6 rules
  • mcp__email-signatures__design_signatures outbound
  • mcp__email-signatures__get_signature_playbook private-data, untrusted-input
  • mcp__email-signatures__create_signature outbound
  • mcp__email-signatures__quote_price untrusted-input
  • mcp__email-signatures__get_install_steps private-data, untrusted-input
  • mcp__email-signatures__get_facts private-data, untrusted-input

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/co.prosignature/email-signatures/verify?hash=e2cfae2c100bcd9fb65784a13feae364d55e5a0f353f689be86b39b64ae132cc" | jq -e '.changed == false'

Pinned hash e2cfae2c100b, from Nov 20, 2026, 11:17 UTC.

Watch

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

https://radar.anlyon.com/servers/co.prosignature/email-signatures/changes.xml

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

Badge

Anlyon Radar badge for co.prosignature/email-signatures
[![Anlyon Radar](https://radar.anlyon.com/badge/co.prosignature/email-signatures.svg)](https://radar.anlyon.com/servers/co.prosignature/email-signatures)

Source: MCP Registry · repository. Synced Nov 6, 2026, 11:17 UTC.

ProSignature email signatures MCP server: questions and answers

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

Is the ProSignature email signatures MCP server safe?

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

Can the ProSignature email signatures MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ProSignature email signatures MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ProSignature email signatures MCP server have?

7 tools: 2 write, 5 read. design_signatures, create_signature, get_signature_playbook, list_layouts, quote_price, get_install_steps and get_facts.

Does the ProSignature email signatures MCP server need sign-in or OAuth?

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

Does the ProSignature email signatures MCP server send data to outside services?

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

Has the ProSignature email signatures MCP server changed its tools?

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