Jotform vs blue·auth Document Signing
Jotform is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). 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-17. 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 | ||
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.0 Forks (GitHub): 1 158 Stars (GitHub): 11 894 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | 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 | Jotform | blue·auth Document Signing |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 11 894 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 158 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.jotform.com) | Remote server (blueauth.co/api/mcp-server/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cursor/plugins | 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) | Not responding since 2026-10-16 | Responded 42 h 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
Jotform
Create and edit forms, then read submissions.
blue·auth Document Signing
Send AI-created PDFs for signature, track signers, and return verifiable document evidence.
How to run each
Jotform
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
blue·auth Document Signing As a remote MCP server
claude mcp add --transport http blueauth-document-signing https://blueauth.co/api/mcp-server/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of blue·auth Document Signing responded at the last daily 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Jotform · What it can do: blue·auth Document Signing · Compare two other plugins
Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. 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.