ProspectAPIs vs CADE: Processos
ProspectAPIs is an MCP server published by ProspectAPIs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). CADE: Processos is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  ProspectAPIs |  CADE: Processos |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.4 Downloads/month (npm): 995 Downloads/week (npm): 245 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.2.5 Downloads/month (npm): 995 Downloads/week (npm): 245 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
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 | ProspectAPIs | CADE: Processos |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-21 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (api.mcp.ai/p_cade_processos) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/prospectapis/prospectapis-mcp | github.com/mcp-dir/cade_processos-mcp |
| Changes in the last 7 days (differs) | 5 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Responded 6 days 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
ProspectAPIs
MCP server for prospectapis.com: funding rounds and cited prospect research briefs.
CADE: Processos
CADE: Court Cases, official-source lookup. Platform-hosted, pay per query with prepaid credit.
How to run each
ProspectAPIs 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
CADE: Processos As a remote MCP server
claude mcp add --transport http cade-processos-mcp https://api.mcp.ai/p_cade_processosCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only CADE: Processos 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
The marketplaces of CADE: Processos publish no settings it asks for, so we do not compare settings.
What it can do: ProspectAPIs · What it can do: CADE: Processos · 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.