Ext Ops Panel
Open dashboard
Comparison

LinkedIn vs WerkCV – Dutch CV check

LinkedIn is an MCP server published by stickerdaniel. Marketplaces we read that list it: 1 (Docker MCP Catalog). WerkCV – Dutch CV check is an MCP server published by werkcv.nl. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
MarketplaceLinkedInWerkCV – Dutch CV check
Docker MCP Catalog Listed
Version: sha256:c437eb638f80
Forks (GitHub): 706
Stars (GitHub): 4 016
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.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

LinkedIn vs WerkCV – Dutch CV check
FactLinkedInWerkCV – Dutch CV check
Marketplaces that list it11
Stars (GitHub) (differs)4 016 (better)0 (worse)
Forks (GitHub) (differs)706 (better)0 (worse)
Last release (differs)Not published2026-10-17
Where it runs (differs)On your machine (stickerdaniel/linkedin-mcp-server:1.4.0)Remote server (werkcv.nl/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-servergithub.com/dk017/werkcv-mcp
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-16
Endpoint at the last check (differs)no remote endpoint we checkResponded 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

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.

WerkCV – Dutch CV check

In its own words, on Official MCP Registry:

Check a CV against Dutch hiring norms, compare it with a vacancy, and open it in WerkCV.

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)

WerkCV – Dutch CV check As a remote MCP server

Claude Code
claude mcp add --transport http cv-check https://werkcv.nl/api/mcp

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

Only WerkCV – Dutch CV check has a remote endpoint we check. How we check endpoints

Tools each declares

Only LinkedIn has

  • close_session
  • get_company_profile
  • get_job_details
  • get_person_profile
  • get_recommended_jobs
  • search_jobs

Only WerkCV – Dutch CV check has

  • check_cv
  • match_vacancy
  • open_in_editor

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (WerkCV – Dutch CV check as of 2026-10-22). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of WerkCV – Dutch CV check publish no settings it asks for, so we do not compare settings.

What it can do: LinkedIn · What it can do: WerkCV – Dutch CV check · 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