Ext Ops Panel
Open dashboard
Comparison

LinkedIn vs emprego.com job search

LinkedIn is an MCP server published by stickerdaniel. Marketplaces we read that list it: 1 (Docker MCP Catalog). emprego.com job search is an MCP server published by emprego.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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

Where each is published
MarketplaceLinkedInemprego.com job search
Docker MCP Catalog Listed
Version: sha256:c437eb638f80
Forks (GitHub): 710
Stars (GitHub): 4 025
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

LinkedIn vs emprego.com job search
FactLinkedInemprego.com job search
Marketplaces that list it11
Stars (GitHub) (differs)4 025No figure on GitHub
Forks (GitHub) (differs)710No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (stickerdaniel/linkedin-mcp-server:1.4.0)Remote server (emprego.com/api/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/stickerdaniel/linkedin-mcp-serverNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-25

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

LinkedIn

In its own words, on Docker MCP Catalog:

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.

emprego.com job search

In its own words, on Official MCP Registry:

Search live job openings in many countries and languages, and read a full job ad.

How to run each

LinkedIn As a local MCP server: Docker image

Claude Code
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)

emprego.com job search As a remote MCP server

Claude Code
claude mcp add --transport http jobs https://emprego.com/api/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only emprego.com job search has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of emprego.com job search publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of emprego.com job search publish no settings it asks for, so we do not compare settings.

What it can do: LinkedIn · What it can do: emprego.com job search · 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.

Where the data comes from: how the catalog is built