Productivity · Remote MCP server

Quicksign

E-signatures for contracts and NDAs. Draft with AI, review, and send for signature.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.causehacker/quicksign
Version
0.1.1
Status
Active
Category
productivity
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-03-15
Updated
2026-03-15
Publisher
causehacker (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/causehacker) · how
Repository
github.com/causehacker/QuickSign
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://quicksign.pro/api/mcp/sseNone

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 200)
Handshake
QuickSign 1.0.0 · protocol 2025-06-18
Tools discovered
4: push_draft_text, get_draft_status, get_draft_content, get_handoff_link
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npm@quicksign/mcp0.1.1stdioNone declared

How to connect Quicksign

Quicksign is a remote MCP server: there is nothing to install. Its endpoint is https://quicksign.pro/api/mcp/sse, 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.

It can also run locally from a Node.js package published to the npm registry: @quicksign/mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @quicksign/mcp@0.1.1.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "quicksign": {
      "command": "npx",
      "args": [
        "-y",
        "@quicksign/mcp@0.1.1"
      ]
    }
  }
}

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

All 2,706 →
ServerRunsEndpoint or package
Quality Control Plan GeneratorQuality control plans from drawing PDFs: auto-extracted tolerances, balloons, Excel + PDF reports.Local · stdionpm: quality-control-plan-mcp
QuantdataFour market-statistics tools + a free qd_ key by email: 1 anonymous look, then 10 calls/UTC day.Remote · HTTPLive check: ✓ handshakeapi.quantdata.uk
QuarterbackStrategic task prioritization and agent orchestration for multi-project operators.Local · stdioPyPI: quarterback
QuibblyYour LinkedIn inbox, connections and video views for AI. Works with any CRM. Drafts only.Remote · HTTPLive check: sign-in requiredserver.quibbly.co
QuietaFamily calendar MCP server: read the family's week and propose changes a parent approves.Remote · HTTPLive check: sign-in requiredgetquieta.app
QuillHubMeeting transcripts for AI agents: search calls, read who said what, transcribe files and links.Remote · HTTPLive check: sign-in requiredmcp.quillhub.ai
Quillpdf MCPLocal-first PDF tools (merge, split, rotate, watermark, Bates, metadata) as MCP server + CLI.Local · stdionpm: quillpdf-mcp
QY Evolution Engine13 tools for agents: pitfalls, results, tasks, capability. Anonymous reads; writes need signing.Remote · HTTPLive check: ✓ handshakeqianyuan.ltd