Ext Ops Panel
Open dashboard
Comparison

job-search vs JobDataLake

job-search is a plugin bundle for AI coding tools published by elliottdehn. Marketplaces we read that list it: 1 (Community GitHub marketplaces). JobDataLake is an MCP server published by echojobsio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
Marketplacejob-searchJobDataLake
Community marketplace elliottdehn/open-jobs Listed
Version: 0.1.0
Forks (GitHub): 45
Stars (GitHub): 388
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.14
Downloads/month (npm): 239
Downloads/week (npm): 51
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

job-search vs JobDataLake
Factjob-searchJobDataLake
Marketplaces that list it11
Stars (GitHub) (differs)388 (better)2 (worse)
Forks (GitHub) (differs)45 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@jobdatalake/mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/elliottdehn/open-jobsgithub.com/echojobsio/jdl-mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-10-172026-10-11

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

job-search

In its own words, on Community GitHub marketplaces:

Local-first semantic job search over the Open Jobs dataset (~3M postings, crawled daily) with freshness, ghost, and date-bump detection no job board provides.

JobDataLake

In its own words, on Official MCP Registry:

Search 1M+ enriched job listings. Filter by skills, salary, location, and more. Free.

How to run each

job-search As a Claude Code plugin

Claude Code
/plugin marketplace add elliottdehn/open-jobs
/plugin install job-search@open-jobs

JobDataLake As a local MCP server: npm package

Claude Code
claude mcp add --env "JDL_API_KEY=<YOUR_JDL_API_KEY>" --transport stdio jdl-mcp-server -- npx -y @jobdatalake/mcp-server

Requires: JDL_API_KEY (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: job-search · What it can do: JobDataLake · Compare two other plugins

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.

Where the data comes from: how the catalog is built