io.github.causehacker/quicksign
REMOTE · QUICKSIGN.PRO · 2 COMPONENTS · SCANNED SEP 20
E-signatures for contracts and NDAs. Draft with AI, review, and send for signature.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 949 tokens (~237/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.causehacker/quicksign MCP server?
io.github.causehacker/quicksign is a hosted endpoint at https://quicksign.pro/api/mcp/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · quicksign.pro
claude mcp add --transport http causehacker-quicksign 'https://quicksign.pro/api/mcp/sse'
{
"mcpServers": {
"causehacker-quicksign": {
"url": "https://quicksign.pro/api/mcp/sse"
}
}
} {
"servers": {
"causehacker-quicksign": {
"type": "http",
"url": "https://quicksign.pro/api/mcp/sse"
}
}
} [mcp_servers.causehacker-quicksign] url = "https://quicksign.pro/api/mcp/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"causehacker-quicksign": {
"type": "remote",
"url": "https://quicksign.pro/api/mcp/sse",
"enabled": true
}
}
} openclaw mcp add causehacker-quicksign --url 'https://quicksign.pro/api/mcp/sse' --transport streamable-http
mcp_servers:
causehacker-quicksign:
url: "https://quicksign.pro/api/mcp/sse" {
"McpServers": {
"causehacker-quicksign": {
"Transport": "http",
"Url": "https://quicksign.pro/api/mcp/sse"
}
}
} assistant mcp add causehacker-quicksign -t streamable-http -u 'https://quicksign.pro/api/mcp/sse'
{
"mcpServers": {
"causehacker-quicksign": {
"type": "http",
"url": "https://quicksign.pro/api/mcp/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://quicksign.pro/api/mcp/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quicksign.pro | CN=YE1,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 667b2a3b987d4714ba79233e638641c8df9 |
| SANs: quicksign.pro | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of quicksign.pro. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pro. | present | 42154 | 8 | Verified |
| quicksign.pro. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://quicksign.pro/api/mcp/sse | Verified | 200 | |
| http (plaintext) | http://quicksign.pro/api/mcp/sse | HTTPS enforced | 301 | https://quicksign.pro:443/api/mcp/sse |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_draft_content ~100
Retrieve the full text content of a previously pushed draft by its session ID. Use this when you have a QuickSign session/document ID and need to read the current draft text — for example, to revise a contract, check what was previously sent, or continue working on an existing draft. Returns the full markdown/text content along with metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The AI Session ID (returned from push_draft_text or shared by the user) |
No output schema declared.
No examples provided.
get_draft_status ~126
Check the full status chain of a document draft in QuickSign. Returns the session status (active/completed), the linked document's lifecycle status (draft/ready/pending/completed/cancelled), and whether the draft or document was converted into a reusable template (converted_to_template, template_id). Use this to follow up on a draft you previously pushed — e.g. "has the owner reviewed that NDA yet?"
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The AI Session ID returned from push_draft_text |
| type | string | yes | Whether this was a PDF or text draft |
No output schema declared.
No examples provided.
get_handoff_link ~94
Get a direct link for the document owner to review a draft in QuickSign. Returns a URL that opens the document directly in the QuickSign editor. Share this with the user so they can review the contract, add recipients, place signature fields, and send it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The document ID to get the review link for |
| type | string | yes | Whether this was a PDF or text draft |
No output schema declared.
No examples provided.
push_draft_text ~196
Send a contract or agreement to QuickSign for e-signature. Drafts an NDA, freelance agreement, consulting contract, SOW, or any document that needs to be signed. Takes your drafted text (markdown, plain text, or HTML) and creates a professional PDF in QuickSign. The document owner reviews it, adds recipients, places signature fields, and sends it for e-signature. Use this whenever a user needs to get a document signed, send a contract for signature, or create any agreement that requires e-signatures. Markdown format is recommended for best results — headings, bold, lists, and tables are all supported. Maximum length: 500,000 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Full contract text content in the specified format |
| content_type | string | – | Content format — markdown recommended |
| title | string | yes | Contract title (e.g., 'Freelance Agreement - Jane Smith') |
No output schema declared.
No examples provided.
What is the io.github.causehacker/quicksign MCP server?
io.github.causehacker/quicksign is an MCP server listed in the public MCP registry as io.github.causehacker/quicksign. E-signatures for contracts and NDAs. Draft with AI, review, and send for signature. This page covers its hosted endpoint (https://quicksign.pro/api/mcp/sse).
Is the io.github.causehacker/quicksign MCP server safe to use?
io.github.causehacker/quicksign scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.causehacker/quicksign MCP server expose?
io.github.causehacker/quicksign exposes 4 tools: push_draft_text, get_draft_status, get_draft_content, get_handoff_link. Their descriptions and schemas cost roughly 516 tokens of context every time the server is loaded.
Does the io.github.causehacker/quicksign MCP server require authentication?
No. We connected to io.github.causehacker/quicksign without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.causehacker/quicksign MCP server still maintained?
io.github.causehacker/quicksign is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.