ProSignature email signatures
REMOTE · PROSIGNATURE.CO
Build free email signatures, quote Pro and Teams prices, get install steps. Read-only, no account.
Available components
Last scanned (5 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Marketing and SEO
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 767 tokens (~153/item across 5 items; 5 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 70
First indexed and scored.
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 23 Oct 2026 · Probed https://prosignature.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=prosignature.co | CN=YE1,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 537113728131f69c78f1572b901b7448638 |
| SANs: prosignature.co, www.prosignature.co | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of prosignature.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| prosignature.co. | 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=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://prosignature.co/mcp | Verified | 200 | |
| http (plaintext) | http://prosignature.co/mcp | HTTPS enforced | 301 | https://prosignature.co/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 →
create_signature Create an email signature (free, no account) ~268
Builds the email-safe HTML signature (table + inline styles, the same bytes as prosignature.co/email-signature-generator) for one person. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| colour | string | – | Accent colour #rrggbb (default #E8604C); the page offers #E8604C, #2B6CB0, #2F855A, #6B46C1, #2B2620, #B7791F |
| company | string | – | Company or business name |
| string | – | Email address | |
| layout | string | – | Layout id (default classic) |
| name | string | yes | Full name (required) |
| phone | string | – | Phone, as it should read; the tel: link keeps digits and + |
| title | string | – | Job title |
| website | string | – | Website: bare domain (https:// is added) or an http(s) URL |
No output schema declared.
No examples provided.
get_facts ProSignature facts ~83
What ProSignature is, the free plan and its credit line, Pro and Teams prices (verified 2026-10-18), how Gmail and Google Workspace installs work per person, 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_install_steps Install steps for a mail client ~92
How a signature from create_signature gets into 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. The free Chrome extension (auto-updates, covers replies) needs the human to sign up first.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | Which mail client |
No output schema declared.
No examples provided.
list_layouts List layouts and colours ~32
The four signature layouts (id, name, what it looks like) and the six accent colours the generator offers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quote_price Quote a ProSignature price ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| billing | string | – | Billing period (default yearly) |
| people | integer | – | How many people, admin included (default 1) |
| plan | string | yes | pro = one person; teams = a company (admin + employees) |
No output schema declared.
No examples provided.
How do I install the ProSignature email signatures MCP server?
ProSignature email signatures is a hosted endpoint at https://prosignature.co/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 · prosignature.co
claude mcp add --transport http co-prosignature-email-signatures 'https://prosignature.co/mcp'
What is the ProSignature email signatures MCP server?
ProSignature email signatures is an MCP server listed in the public MCP registry as co.prosignature/email-signatures. Build free email signatures, quote Pro and Teams prices, get install steps. Read-only, no account. This page covers its hosted endpoint (https://prosignature.co/mcp).
Is the ProSignature email signatures MCP server safe to use?
ProSignature email signatures scores 72 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 ProSignature email signatures MCP server expose?
ProSignature email signatures exposes 5 tools: create_signature, list_layouts, quote_price, get_install_steps, get_facts. Their descriptions and schemas cost roughly 626 tokens of context every time the server is loaded.
Does the ProSignature email signatures MCP server require authentication?
No. We connected to ProSignature email signatures without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ProSignature email signatures MCP server still maintained?
ProSignature email signatures is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.