Ext Ops Panel
Open dashboard
Comparison

Docusign vs x402 Email Verifier

Docusign is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). x402 Email Verifier is an MCP server published by x402-email-verifier.microtools-x402.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceDocusignx402 Email Verifier
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 268
Stars (GitHub): 12 913
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
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

Docusign vs x402 Email Verifier
FactDocusignx402 Email Verifier
Marketplaces that list it11
Stars (GitHub) (differs)12 913 (better)0 (worse)
Forks (GitHub) (differs)1 268 (better)0 (worse)
Last release (differs)Not published2026-10-17
Where it runs (differs)Remote server (mcp.docusign.com/mcp)Remote server (x402-email-verifier.microtools-x402.workers.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.com/shaimaiiee-design/x402-email-verifier
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-17
Endpoint at the last check (differs)Answered with HTTP 403 (5 days ago)not checked yet

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

In its own words, on Cursor: cursor/plugins:

Manage envelopes, templates, workflows, and agreements.

x402 Email Verifier

In its own words, on Official MCP Registry:

Email verification for AI agents: syntax, MX, disposable, role, score. $0.001 USDC/call via x402.

How to run each

Docusign

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

x402 Email Verifier As a remote MCP server

Claude Code
claude mcp add --transport http email-verifier https://x402-email-verifier.microtools-x402.workers.dev/mcp

Commands 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: x402 Email Verifier · 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.

Where the data comes from: how the catalog is built