Productivity · Remote MCP server
SignatureAPI
E-signature API: send documents for signature, track envelopes, get signed files.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.signatureapi/mcp- Version
- 1.0.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-09-25
- Updated
- 2026-09-25
- Publisher
- com.signatureapi
- Namespace
- Namespace verified by the MCP Registry via the domain signatureapi.com · how
- Website
- signatureapi.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.signatureapi.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect SignatureAPI
SignatureAPI is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.signatureapi.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| Sign CliAgent-first e-signature MCP server with offline PAdES signing and hash-chained audit. | Local · stdio |
| Signal not NoiseAI-driven daily-focus todo app on your phone (max 3/day). View & add todos from any MCP client. | Remote · HTTPLive check: sign-in required |
| SignalizB2B lead generation, email verification, company enrichment, and agentic GTM Ops. | Remote · HTTPLive check: sign-in required |
| SignatoroMake email signatures, get install steps for your mail app, and manage your company's signatures. | Remote · HTTPLive check: ✓ handshake |
| SignatureForeverAudit and build email signatures that survive Gmail, Outlook desktop and Apple Mail. | Remote · HTTPLive check: ✓ handshake |
| SignforgeSend documents for e-signature from AI agents. Upload, sign, and download PDFs. | Local · stdio |
| SignNow MCP ServerA MCP server that gives AI agents access to SignNow eSignature workflows over STDIO. | Local · stdio |
| SignSimpleSend PDFs for legally binding e-signature, free and unlimited. Track status; free legal templates. | Remote · HTTPLive check: ✓ handshake |