Signeasy

Yes, by three separate tools. signeasy_create_signature_request emails signers, signeasy_send_reminder emails whoever has not yet signed, and signeasy_cancel_request voids the request and notifies people too. Signeasy's API docs confirm each sends email. None of those emails can be recalled once the call returns.

Anthropic's directory lists 27, and Signeasy's own MCP documentation describes 32. All 27 directory names appear in the docs, so the gap runs one way: the directory under-lists by five. Two of the five change state — signeasy_approve_request releases a request to its signers and signeasy_decline_request kills the envelope outright — so the directory omits exactly the terminal actions a reader most needs to see.

Signeasy states that anything emailing people or changing the account asks you to confirm first. That prompt covers the call, not its consequences. Approving a create_signature_request means an email leaves for a named counterparty immediately, and nothing in the tool surface unsends it — only a cancel that emails them again.

Ten, and they are real application scopes rather than identity claims. The resource descriptor lists user:read, original:read, original:create, rs:read, rs:create, rs:update, signed:read, template:manage, repository:read and offline_access. Crucially rs:create and rs:read are separate, so a read-only grant is genuinely possible here.

No tool among the 32 documented names carries a delete verb, but one requested scope grants deletion anyway. Signeasy's scopes table states template:manage grants read, list, rename and delete access to all your templates, while only two read-only template tools exist. The grant is wider than the tool surface uses.

Cancel is the sender's action and decline is the recipient's. signeasy_cancel_request voids a request you sent, triggering Signeasy's rs.voided event. signeasy_decline_request rejects a request sent to you, moving the envelope to recipient_declined so nobody else can sign it. Both are terminal and neither appears reversible.

The path is named /sse but the transport is streamable HTTP, which Anthropic's directory also records. A POST initialize to https://mcp.signeasy.com/mcp/sse returned an HTTP 401 JSON body rather than an event stream on 2026-08-22. Use the URL exactly as published; the suffix does not mean legacy SSE transport.

Yes. Signeasy documents 80 requests per minute globally, a burst limit of 20 requests per 10 seconds, and HTTP 429 with Too Many Requests when you exceed either. Signeasy recommends waiting a minute before retrying. Its sandbox separately caps envelope creation at 50 per hour.