CrustAPI Google + LinkedIn Data vs LinkFetch: LinkedIn MCP
CrustAPI Google + LinkedIn Data is an MCP server published by crustapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). LinkFetch: LinkedIn MCP is an MCP server published by linkfetch.io. 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 |  CrustAPI Google + LinkedIn Data |  LinkFetch: LinkedIn MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.2 Downloads/month (npm): 250 Downloads/week (npm): 45 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.0.1 Downloads/month (npm): 622 Downloads/week (npm): 189 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 | CrustAPI Google + LinkedIn Data | LinkFetch: LinkedIn MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (crustapi-mcp) | Remote server (linkfetch.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/crustapi/crustapi-mcp | github.com/ffucucuoglu/linkedin-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 43 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
CrustAPI Google + LinkedIn Data
Live Google + public LinkedIn data: search, maps, profiles, companies, jobs. Pay only for results.
LinkFetch: LinkedIn MCP
LinkedIn jobs, companies and people for AI agents, plus messages and invites via your own account.
How to run each
CrustAPI Google + LinkedIn Data As a local MCP server: npm package
claude mcp add --env "CRUSTAPI_API_KEY=<YOUR_CRUSTAPI_API_KEY>" --transport stdio search -- npx -y crustapi-mcpRequires: CRUSTAPI_API_KEY (secret)
LinkFetch: LinkedIn MCP As a remote MCP server
claude mcp add --transport http linkedin https://linkfetch.io/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: LINKFETCH_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only LinkFetch: LinkedIn MCP 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
Only CrustAPI Google + LinkedIn Data asks for
CRUSTAPI_API_KEY (secret)
Only LinkFetch: LinkedIn MCP asks for
LINKFETCH_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: CrustAPI Google + LinkedIn Data · What it can do: LinkFetch: LinkedIn MCP · Compare two other plugins
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.