LinkedIn vs regdata-company-lookup
LinkedIn is an MCP server published by stickerdaniel. Marketplaces we read that list it: 1 (Docker MCP Catalog). regdata-company-lookup is a plugin bundle for AI coding tools published by nolpak14. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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 |  regdata-company-lookup |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c437eb638f80 Forks (GitHub): 674 Stars (GitHub): 3 859 Not marked · First seen |
Not listed |
| Community marketplace nolpak14/getregdata | Not listed | Listed Version: not stated Forks (GitHub): 0 Stars (GitHub): 6 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 | regdata-company-lookup | |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 859 (better) | 6 (worse) |
| Forks (GitHub) (differs) | 674 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (stickerdaniel/linkedin-mcp-server:1.4.0) | On your machine (getregdata-mcp) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 1, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 29 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/stickerdaniel/linkedin-mcp-server | github.com/nolpak14/getregdata |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
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.
regdata-company-lookup
Free company lookups straight from official public APIs across 28 jurisdictions plus global LEI resolution - no Apify token and no per-result cost. Resolve and verify a company by name or national identifier.
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)
regdata-company-lookup As a Claude Code plugin
/plugin marketplace add nolpak14/getregdata
/plugin install regdata-company-lookup@getregdataCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of regdata-company-lookup publish no list of tools, so we do not compare tools.
Settings each asks for
Only LinkedIn asks for
LINKEDIN_COOKIE (secret)USER_AGENT
Only regdata-company-lookup asks for
APIFY_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: LinkedIn · What it can do: regdata-company-lookup · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.