Docusign vs PDF Verify (PDF Agent Stack)
Docusign is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). PDF Verify (PDF Agent Stack) is an MCP server published by shuji-bonji. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  PDF Verify (PDF Agent Stack) | |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.0 Forks (GitHub): 1 197 Stars (GitHub): 12 306 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.31.0 Downloads/month (npm): 1 728 Downloads/week (npm): 412 Forks (GitHub): 0 Stars (GitHub): 0 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 | Docusign | PDF Verify (PDF Agent Stack) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 306 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 197 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Remote server (mcp.docusign.com/mcp) | On your machine (@shuji-bonji/pdf-verify-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| 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/shuji-bonji/pdf-verify-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 403 (3 days ago) | no remote endpoint we check |
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
Docusign
Manage envelopes, templates, workflows, and agreements.
PDF Verify (PDF Agent Stack)
Verify PDF signatures, detect tampering, and identify PDF/A and PAdES conformance levels.
How to run each
Docusign
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
PDF Verify (PDF Agent Stack) As a local MCP server: npm package
claude mcp add --transport stdio pdf-verify-mcp -- npx -y @shuji-bonji/pdf-verify-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Docusign 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Docusign · What it can do: PDF Verify (PDF Agent Stack) · 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.