LinkedIn vs VOYGR Prospecting
LinkedIn is an MCP server published by stickerdaniel. Marketplaces we read that list it: 3 (Docker MCP Catalog, PyPI (MCP servers), Community GitHub marketplaces). VOYGR Prospecting is an MCP server published by voygr-tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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 |  LinkedIn |  VOYGR Prospecting |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c437eb638f80 Forks (GitHub): 743 Stars (GitHub): 4 179 Not marked · First seen |
Not listed |
| PyPI (MCP servers) | Listed Version: 4.29.0 Downloads/month (PyPI): 68 344 Downloads/week (PyPI): 8 301 Forks (GitHub): 743 Stars (GitHub): 4 179 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.3 Forks (GitHub): 0 Stars (GitHub): 2 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 | VOYGR Prospecting | |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 4 179 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 743 (better) | 0 (worse) |
| Last release (differs) | 2026-11-01 (worse) | 2026-11-07 (better) |
| Where it runs (differs) | On your machine (stickerdaniel/linkedin-mcp-server:1.4.0) | Remote server (api.voygr.tech/places/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 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/stickerdaniel/linkedin-mcp-server | github.com/voygr-tech/prospecting |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-04 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 45 h ago returned HTTP 405 |
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.
VOYGR Prospecting
Find 16M+ US businesses by city/category; build lead lists with owners, contacts, status and hours.
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.0Requires: LINKEDIN_COOKIE (secret)
VOYGR Prospecting As a remote MCP server
claude mcp add --transport http prospecting https://api.voygr.tech/places/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only VOYGR Prospecting has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of VOYGR Prospecting publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of VOYGR Prospecting publish no settings it asks for, so we do not compare settings.
What it can do: LinkedIn · What it can do: VOYGR Prospecting · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.