gia-prospecting-engine vs HeyLead — AI agent for LinkedIn outreach
gia-prospecting-engine is a plugin bundle for AI coding tools published by knowledgepa3. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). HeyLead — AI agent for LinkedIn outreach is an MCP server published by D4umak. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  gia-prospecting-engine |  HeyLead — AI agent for LinkedIn outreach |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.10.463 Downloads/month (PyPI): 18 565 Downloads/week (PyPI): 3 319 Forks (GitHub): 0 Stars (GitHub): 11 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 | gia-prospecting-engine | HeyLead — AI agent for LinkedIn outreach |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 11 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (heylead.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/knowledgepa3/gia-prospecting-engine | github.com/d4umak/linkedin-outreach-mcp |
| Changes in the last 7 days (differs) | 0 | 18 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago, requires a key |
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
gia-prospecting-engine
AI-powered lead generation and outreach automation for Claude Code and Cowork. Find companies hiring in your target market, research prospects, and draft personalized cold emails — all in parallel. Powered by GIA governance.
HeyLead — AI agent for LinkedIn outreach
AI agent for LinkedIn outreach: finds the right people, writes in your voice, follows up, replies.
How to run each
gia-prospecting-engine As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install gia-prospecting-engine@claude-communityHeyLead — AI agent for LinkedIn outreach As a remote MCP server
claude mcp add --transport http heylead https://heylead.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only HeyLead — AI agent for LinkedIn outreach 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: gia-prospecting-engine · What it can do: HeyLead — AI agent for LinkedIn outreach · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.