Ext Ops Panel
Open dashboard
Comparison

io.github.aidocx/mcp-server vs io.github.causehacker/quicksign

io.github.aidocx/mcp-server is an MCP server published by aidocx. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.causehacker/quicksign is an MCP server published by causehacker. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.aidocx/mcp-serverio.github.causehacker/quicksign
Official MCP Registry Listed
Version: 0.3.1
Downloads/month (npm): 226
Downloads/week (npm): 29
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (npm): 104
Downloads/week (npm): 22
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.aidocx/mcp-server vs io.github.causehacker/quicksign
Factio.github.aidocx/mcp-serverio.github.causehacker/quicksign
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (aidocx-mcp-server)Remote server (quicksign.pro/api/mcp/sse)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 2Not published
LicenceNot statedNot stated
Repository (differs)github.com/aidocx/mcp-servergithub.com/causehacker/quicksign
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (16 h ago)

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.aidocx/mcp-server

In its own words, on Official MCP Registry:

Create, upload, and manage contracts from AI assistants. AI analysis and e-signatures.

io.github.causehacker/quicksign

In its own words, on Official MCP Registry:

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

How to run each

io.github.aidocx/mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "AIDOCX_API_KEY=<YOUR_AIDOCX_API_KEY>" --env "AIDOCX_API_SECRET=<YOUR_AIDOCX_API_SECRET>" --transport stdio io-github-aidocx-mcp-server -- npx -y aidocx-mcp-server

Requires: AIDOCX_API_KEY (secret), AIDOCX_API_SECRET (secret)

io.github.causehacker/quicksign As a remote MCP server

Claude Code
claude mcp add --transport http quicksign https://quicksign.pro/api/mcp/sse

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.causehacker/quicksign has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.causehacker/quicksign publish no settings it asks for, so we do not compare settings.

What it can do: io.github.aidocx/mcp-server · What it can do: io.github.causehacker/quicksign · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built