Ecommerce Data API vs ProspectAPIs
Ecommerce Data API is an MCP server published by ecommercedataapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  Ecommerce Data API |  ProspectAPIs |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
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
| Fact | Ecommerce Data API | ProspectAPIs |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-27 |
| Where it runs (differs) | Remote server (ecommercedataapi.com/mcp) | Remote server or your machine |
| Transport (differs) | Streamable HTTP | Streamable HTTP, stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/ecommercedataapi/ecommerce-data-api | github.com/prospectapis/prospectapis-mcp |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen (differs) | 2026-10-15 | 2026-10-12 |
| Endpoint at the last check (differs) | Responded 25 h ago, requires a key | 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
Ecommerce Data API
Amazon product, keyword, sales estimate, reverse ASIN, market and trademark data for agents.
ProspectAPIs
MCP server for prospectapis.com: funding rounds and cited prospect research briefs.
How to run each
Ecommerce Data API As a remote MCP server
claude mcp add --transport http ecommerce-data-api https://ecommercedataapi.com/mcpProspectAPIs As a remote MCP server
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.
Both endpoints 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 Ecommerce Data API publish no settings it asks for, so we do not compare settings.
What it can do: Ecommerce Data API · What it can do: ProspectAPIs · Compare two other plugins
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.