Signathing e-signature

com.signathingPublished by signathing.comOfficial publisherv1.1.1Updated Nov 6, 2026

Send PDFs for e-signature from AI agents, with a public hash-chained evidence log anyone can verify

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an AI assistant send PDFs for e-signature, track signers, and pull a publicly verifiable evidence package.

What you can do
  • Send a PDF by URL or base64, name signers and view-only recipients, and place signature, initials, date, text, checkbox or dropdown fields
  • Check status, signer viewed and signed times, download links and event history, and list recent documents by status
  • Remind unsigned recipients, void an open document, or extend an expired one by 14 days
  • Read prepaid balance and monthly usage, and fetch the evidence package with PDF hashes and public log positions
  • Look up the verification code stamped beside a Signathing signature on any document
When to use it
Useful when an assistant should send agreements, leases or other PDFs out for signature and later confirm completion with evidence that a third party can check, rather than relying on the sender's own logs.
Requirements
A remote Streamable HTTP endpoint; no local package needed, though a bridge exists for stdio-only clients. Authentication is OAuth sign-in or an API key sent as an Authorization bearer header, created in the Signathing dashboard. A Signathing account is required; the free tier covers 100 documents a month.
Before you install
Sending documents emails real people and creates legally meaningful signing requests; voiding, reminding and extending change live documents. Per-signer card payment collection and government ID verification are billed, and ID checks cost $2 per attempt from the prepaid balance. Usage beyond the free tier is charged per document. The API key is a live secret and should be kept out of shared configs.

Installation

In SourceWeft

  1. Open Signathing e-signature in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.signathing%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "signathing-e-signature": {
      "type": "http",
      "url": "https://signathing.com/api/mcp"
    }
  }
}

README

Signathing MCP server

Send PDFs for e-signature from any AI agent, with ESIGN and UETA consent captured on every signature, and get back a certified copy whose history anyone can verify without trusting the sender or Signathing.

  • Remote server: https://signathing.com/api/mcp (Streamable HTTP). Sign in with OAuth, or send an API key as a bearer header.
  • Free tier: 100 documents a month, no card. Then $0.06 a document (101 to 500), $0.03 (501 to 3,000), $0.025 (3,001+), prepaid.
  • Evidence: every signing event is appended to a public hash chain, sealed daily and archived with the Internet Archive. signathing.com/transparency
  • Docs: signathing.com/developers · OpenAPI: /api/v1/openapi.json · /llms.txt

Operated by AllContraX LLC, Kentucky, USA. The Signathing app and website stay free for people; the API and MCP server are for software.

Tools

ToolWhat it does
send_documentUpload a PDF (https URL or base64), name up to 25 signers and 25 view-only recipients, optionally place signature, initials, date, name, email, text, number, checkbox, radio or dropdown fields. Signers get a private link by email (and text). Per signer, payment_amount_cents collects a card payment after they sign (into the sender's own Stripe account, no platform fee; the document completes when paid) and id_verification: true requires a government ID plus selfie check before signing ($2 an attempt from the prepaid balance). One billable unit.
get_documentStatus, signers with viewed/signed times, download links, event history.
list_documentsYour recent documents, filterable by status.
remind_documentRe-send links to everyone who has not signed (once an hour).
void_documentWithdraw an open document. Within 10 minutes of sending, the unit is refunded.
extend_documentGive an expired document 14 more days and fresh links for everyone still waited on.
get_accountPrepaid balance, documents used this month, free documents left, projected run-out.
get_evidenceEvidence package: PDF hashes, every signer and event with its position in the public evidence log, and the recipe to verify it.
verify_signature_codeLook up the code stamped beside any Signathing signature. Works for any document.

Connect

Claude.ai, ChatGPT, Grok apps (OAuth)

Add a custom connector / remote MCP server with the URL https://signathing.com/api/mcp. You will be sent to signathing.com to sign in and approve. Disconnect any time under API in your Signathing dashboard.

Claude Code

bash
claude mcp add --transport http signathing https://signathing.com/api/mcp \  --header "Authorization: Bearer sk_live_..."

Or without a key, using OAuth: claude mcp add --transport http signathing https://signathing.com/api/mcp and run /mcp to sign in.

Cursor, VS Code, Windsurf (mcp.json)

json
{ "mcpServers": { "signathing": {    "url": "https://signathing.com/api/mcp",    "headers": { "Authorization": "Bearer sk_live_..." } } } }

Grok (xAI Responses API)

json
{ "type": "mcp", "server_label": "signathing",  "server_url": "https://signathing.com/api/mcp",  "headers": { "Authorization": "Bearer sk_live_..." } }

Claude API (Messages API, mcp_servers)

json
{ "type": "url", "name": "signathing", "url": "https://signathing.com/api/mcp",  "authorization_token": "sk_live_..." }

stdio-only clients

This repository ships a dependency-free bridge for clients that cannot speak HTTP MCP:

json
{ "mcpServers": { "signathing": {    "command": "npx", "args": ["-y", "github:jacejb/signathing-mcp"],    "env": { "SIGNATHING_API_KEY": "sk_live_..." } } } }

Create a key at signathing.com/dashboard/api.

Why a third party instead of letting the agent sign things itself

A signature only matters on the day it is disputed. On that day the party that controlled the signing system is the party with something to gain, and its own logs are "trust me." Signathing is nobody's party to the contract, and it does not ask you to trust it either: every signing event goes into one public hash chain, each entry commits to the private details through a hash without publishing them, each day is sealed and archived by the Internet Archive, and the verifier in verifier/ recomputes all of it from a document's evidence package.

bash
node verifier/verify-signathing.mjs evidence.json original.pdf signed.pdf

Example: the whole loop, verified

examples/agent-loop.mjs (Node 18+, no dependencies, public domain) sends a PDF, waits for the signature, pulls the evidence package and the certified PDF, recomputes every hash and chain entry, confirms each entry against the public log, and resolves the verification code publicly. It is the loop an agent should run before it treats an agreement as done.

bash
SIGNATHING_API_KEY=sk_live_... node examples/agent-loop.mjs --name "Pat Lee" --email [email protected]
[2] Send for signature  ok   document 71 (sent); billing {"charged_tenths":0,"unit_this_month":1}  ok   server's original_sha256 matches the bytes we sent[3] Waiting for Pat Lee to sign (up to 30 min)  ok   completed at 2026-10-26T02:02:00Z; signed PDF SHA-256 afe6...; sealed=true[4] Evidence package and certified PDF  ok   signed PDF hashes to document.signed_sha256[5] Independent verification  ok   event 609 completed -> chain seq 589  ok   seq 589 is identical in the public log  ok   public log slice 583 to 590 recomputes end to end[6] Public checks anyone can repeat  ok   verification code resolves publicly to this document and its signed hashVERIFIED: document 71, 6 events, all hashes and public-log entries recomputed.

With MCP it is four tool calls: send_document, get_document (or the document.completed webhook), get_evidence, then the verifier on what came back. The day's seal, Internet Archive snapshot and OpenTimestamps proof arrive after midnight UTC; a second verifier run the next day checks those too.

Example: an agent sends a lease

User: Send the lease at https://files.example.com/lease.pdf to Pat Lee ([email protected]) for signature.Agent -> send_document { file_url, title: "Lease", signers: [{ name: "Pat Lee", email: "[email protected]" }] }Signathing -> { id: 58, status: "sent", signers: [{ signing_url: "https://signathing.com/sign/..." }], billing: { charged_tenths: 0 } }

Pat gets an email, signs in the browser, and the agent can call get_document or receive a webhook. The certified PDF is digitally sealed and carries a certificate page and a verification code per signature.

License

MIT for this repository. The Signathing service has its own terms and privacy policy.

Source: README.md at commit d1126a2

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.1LatestOct 30, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts