Ext Ops Panel
Open dashboard
Comparison

saleshandy vs ProspectAPIs

saleshandy is a plugin bundle for AI coding tools published by saleshandy. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ProspectAPIs is an MCP server published by ProspectAPIs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. 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
MarketplacesaleshandyProspectAPIs
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.4
Downloads/month (npm): 995
Downloads/week (npm): 245
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.4.1
Downloads/month (npm): 995
Downloads/week (npm): 245
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

saleshandy vs ProspectAPIs
FactsaleshandyProspectAPIs
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-27
Where it runs (differs)Remote server (mcp.saleshandy.com/mcp)Remote server or your machine
Transport (differs)Streamable HTTPStreamable HTTP, stdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)5Not a bundle
LicenceMITMIT
Repository (differs)github.com/saleshandy/saleshandy-plugingithub.com/prospectapis/prospectapis-mcp
Changes in the last 7 days (differs)06
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)Answered with HTTP 400 (2 h ago)Responded 41 h 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

saleshandy

In its own words, on Claude Code: claude-plugins-community:

Saleshandy prospecting and enrichment for Claude Code — natural-language ICP search and one-shot lead enrichment, wired through the Saleshandy MCP server.

ProspectAPIs

In its own words, on Official MCP Registry:

MCP server for prospectapis.com: funding rounds and cited prospect research briefs.

How to run each

saleshandy As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install saleshandy@claude-community

ProspectAPIs As a remote MCP server

Claude Code
claude mcp add --transport http prospectapis-mcp https://api.prospectapis.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: PROSPECTAPIS_API_KEY (secret), Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of ProspectAPIs 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

The marketplaces of saleshandy publish no settings it asks for, so we do not compare settings.

What it can do: saleshandy · What it can do: ProspectAPIs · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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