io.github.kumarprobeops/signforge vs blue·auth Document Signing
io.github.kumarprobeops/signforge is an MCP server published by kumarprobeops. Marketplaces we read that list it: 1 (Official MCP Registry). blue·auth Document Signing is an MCP server published by ricdanyalgil. 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 |  io.github.kumarprobeops/signforge |  blue·auth Document Signing |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.2 Downloads/month (npm): 172 Downloads/week (npm): 26 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 No figure published 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 | io.github.kumarprobeops/signforge | blue·auth Document Signing |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@signforge/mcp-server) | Remote server (blueauth.co/api/mcp-server/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/kumarprobeops/signforge-mcp | github.com/ricdanyalgil/blueauth |
| 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, requires a key |
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.kumarprobeops/signforge
Send documents for e-signature from AI agents. Upload, sign, and download PDFs.
blue·auth Document Signing
Send AI-created PDFs for signature, track signers, and return verifiable document evidence.
How to run each
io.github.kumarprobeops/signforge As a local MCP server: npm package
claude mcp add --env "SIGNFORGE_API_KEY=<YOUR_SIGNFORGE_API_KEY>" --transport stdio signforge -- npx -y @signforge/mcp-serverRequires: SIGNFORGE_API_KEY (secret)
blue·auth Document Signing As a remote MCP server
claude mcp add --transport http blueauth-document-signing https://blueauth.co/api/mcp-server/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only blue·auth Document Signing 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 blue·auth Document Signing publish no settings it asks for, so we do not compare settings.
What it can do: io.github.kumarprobeops/signforge · What it can do: blue·auth Document Signing · 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.