insaight vs ProspectAPIs
insaight is a plugin bundle for AI coding tools published by Spiros Baxevanakis. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-11-08. 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 | |
|---|---|---|
| Community marketplace spirosbax/insaight | Not seen in the last pass Version: 0.2.0 Forks (GitHub): 3 Stars (GitHub): 34 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed, marked deprecated Version: 0.2.5 Downloads/month (npm): 3 268 Downloads/week (npm): 2 219 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.17.1 Downloads/month (npm): 3 268 Downloads/week (npm): 2 219 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 | insaight | ProspectAPIs |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 34 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-07 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | stdio, Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 9 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/spirosbax/insaight | github.com/prospectapis/prospectapis-mcp |
| Changes in the last 7 days (differs) | 2 | 19 |
| First seen (differs) | 2026-11-06 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 27 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
insaight
LinkedIn prospect intelligence inside Claude. Automates the research behind outreach, not the sending: classifies what people and companies post about, mines comment threads for warm leads, surfaces uncommon commonalities, and learns which hooks earn replies. 18 MCP tools plus 8 skills, all local.
ProspectAPIs
Moved to com.prospectapis/prospectapis-mcp. Install prospectapis-mcp from npm for the latest.
How to run each
insaight As a Claude Code plugin
/plugin marketplace add spirosbax/insaight
/plugin install insaight@insaightProspectAPIs As a local MCP server: npm package
claude mcp add --env "PROSPECTAPIS_API_KEY=<YOUR_PROSPECTAPIS_API_KEY>" --transport stdio prospectapis-mcp -- npx -y prospectapis-mcpRequires: PROSPECTAPIS_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ProspectAPIs 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 insaight publish no settings it asks for, so we do not compare settings.
What it can do: insaight · What it can do: ProspectAPIs · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.