6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Send documents for e-signature, mint signing links and track invites.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The SignNow MCP server lets Claude, ChatGPT or any MCP-compatible agent list templates, create documents, send them for electronic signature and track who has signed. Sixteen tools cover the listed surface. Two of them email a binding signature request to a real person on the call — and six others deliberately mint a link instead of sending anything.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
send_invite and send_invite_from_template have no draft, dry-run or hold parameter in the source. Your MCP client's approval prompt is the only gate.update_document_fields carries destructiveHint: true, so clients keying warnings off that hint will not flag a send.auth_method defaults to none, making a minted link a bearer credential. Set it deliberately.tools/list after connecting.scopes_supported is offline_access and *, so access cannot be narrowed to reads and consent is all-or-nothing.tools/list. The endpoint requires OAuth and this catalogue does not authenticate, so the tool inventory here comes from the directory snapshot and SignNow's public source, not from a handshake.Yes, two of its tools do. `send_invite` and `send_invite_from_template` build a per-recipient email with subject and message, then call SignNow's invite endpoints, which dispatch immediately. The open-source implementation exposes no draft flag, no dry-run parameter and no hold-for-approval option, so a caller cannot request staged behaviour. One call puts mail in a signer's inbox.
No, and that is the connector's best design decision. The six `create_embedded_*` tools mint a signing, sending or editing URL and hand it back to the caller rather than mailing anyone. SignNow documents embedded signing as creating a session without sending an email. One caveat: the embedded invite tool accepts a delivery parameter that can be switched to email.
Not through the sixteen tools Anthropic's directory lists, which contain no cancel operation. SignNow's open-source server does implement a cancel tool that voids all pending invites on a document, and its documentation describes that capability, but it sits outside the listed surface. Cancelling stops pending signers; it does not recall email already delivered or undo completed signatures.
They expire by default and authentication is optional. The embedded sending and editor tools take a link-lifetime parameter defaulting to fifteen minutes in SignNow's API, with sending capped at forty-five minutes. The embedded invite recipient carries an authentication method that defaults to none, so a minted signing link is a bearer credential unless you set it deliberately.
Anthropic's snapshot lists sixteen and those sixteen match SignNow's version 1.0.1 manifest exactly. The current open-source release is version 3.1.0, whose documentation describes roughly twenty-five tools including cancel, reminder, contact search, upload and rename. The listed sixteen are registered as the version 1.0 compatibility layer, so the snapshot reflects a superseded release.
SignNow states its default electronic signature qualifies under both the ESIGN Act and UETA, and that an electronic signature cannot be denied enforceability solely for being electronic. It describes maintaining an audit log for each signing session to support attribution in disputes. Treat that as the vendor's stated position and consult a lawyer about your own use.
SignNow's documentation points at a free developer account rather than a paid tier. Its prerequisites list an account, an active SignNow API application, and credentials comprising an account email, password and application authorization token. No admin enablement switch is documented for the hosted endpoint, which authenticates by OAuth instead of the token-based local setup.
delivery_type and auth_method defaults, fetched 2026-08-19 · retrieved 2026-08-19https://mcp-server.signnow.com/mcp and its RFC 9728 / RFC 8414 metadata, 2026-08-19 · retrieved 2026-08-19Connect SignNow once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.