LinkedIn vs Prospect Intelligence
LinkedIn is an MCP server published by stickerdaniel. Marketplaces we read that list it: 1 (Docker MCP Catalog). Prospect Intelligence is an MCP server published by truepointmarketingpartners-dotcom. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c437eb638f80 Forks (GitHub): 712 Stars (GitHub): 3 938 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.9.1 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 | Prospect Intelligence | |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 938 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 712 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (stickerdaniel/linkedin-mcp-server:1.4.0) | Remote server (prospect-intelligence.prospectintel.workers.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/stickerdaniel/linkedin-mcp-server | github.com/truepointmarketingpartners-dotcom/prospect-intelligence |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 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
This MCP server allows Claude and other AI assistants to access your LinkedIn. Scrape LinkedIn profiles and companies, get your recommended jobs, and perform job searches. Set your li_at LinkedIn cookie to use this server.
Prospect Intelligence
B2B company research and work-email lookup for AI agents. Pay per call in USDC on Base via x402.
How to run each
LinkedIn As a local MCP server: Docker image
claude mcp add --env "LINKEDIN_COOKIE=<YOUR_LINKEDIN_COOKIE>" --transport stdio linkedin-mcp-server -- docker run -i --rm -e LINKEDIN_COOKIE stickerdaniel/linkedin-mcp-server:1.4.0
Requires: LINKEDIN_COOKIE (secret)
Prospect Intelligence As a remote MCP server
claude mcp add --transport http prospect-intelligence https://prospect-intelligence.prospectintel.workers.dev/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Prospect Intelligence has a remote endpoint we check. How we check endpoints
Tools each declares
Only LinkedIn has
close_sessionget_company_profileget_job_detailsget_person_profileget_recommended_jobssearch_jobs
Only Prospect Intelligence has
basic_lookupemail_lookupenriched_lookupfind_emails_batchprospect_briefrun_named_tool
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Prospect Intelligence as of 2026-10-16). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Prospect Intelligence publish no settings it asks for, so we do not compare settings.
What it can do: LinkedIn · What it can do: Prospect Intelligence · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.