Needle vs ZapSign
Needle is an MCP server published by needle-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). ZapSign is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
| Marketplace |  Needle |  ZapSign |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:d3fd314f40c3 Forks (GitHub): 24 Pulls (Docker Hub): 11 676 Stars (Docker Hub): 1 Stars (GitHub): 104 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Forks (GitHub): 0 (last published figure) Stars (GitHub): 0 (last published figure) 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
| Fact | Needle | ZapSign |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 104 | 0 (last published figure) |
| Pulls (Docker Hub) (differs) | 11 676 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 24 | 0 (last published figure) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/needle-mcp) | Remote server (api.mcp.ai/p_zapsign) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 7 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/needle-ai/needle-mcp | github.com/mcp-dir/zapsign-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days 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
Needle
Production-ready RAG service to search and retrieve data from your documents.
ZapSign
ZapSign electronic document signing via the official API: create documents for signature (from PDF,
How to run each
Needle As a local MCP server: Docker image
claude mcp add --env "NEEDLE_API_KEY=<YOUR_NEEDLE_API_KEY>" --transport stdio needle-mcp -- docker run -i --rm -e NEEDLE_API_KEY mcp/needle-mcpRequires: NEEDLE_API_KEY (secret)
ZapSign As a remote MCP server
claude mcp add --transport http zapsign-mcp https://api.mcp.ai/p_zapsignCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ZapSign has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of ZapSign publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of ZapSign publish no settings it asks for, so we do not compare settings.
What it can do: Needle · What it can do: ZapSign · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.