Ext Ops Panel
Open dashboard
Comparison

job-search vs Google Jobs (Apify)

job-search is a plugin bundle for AI coding tools published by Aptiq Labs, Inc.. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Google Jobs (Apify) is an MCP server published by juraam. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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-searchGoogle Jobs (Apify)
Community marketplace agent-data/job-search Listed
Version: 0.9.0
Forks (GitHub): 4
Stars (GitHub): 54
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

job-search vs Google Jobs (Apify)
Factjob-searchGoogle Jobs (Apify)
Marketplaces that list it11
Stars (GitHub) (differs)54No figure on GitHub
Forks (GitHub) (differs)4No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.apify.com)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/agent-data/job-searchNot stated
Changes in the last 7 days22
First seen (differs)2026-10-142026-10-18
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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:

Define your preferences and start your first job search with /job-search.

Google Jobs (Apify)

In its own words, on Official MCP Registry:

Live Google for Jobs postings: salary, apply links, remote and date filters. Pay per job.

How to run each

job-search As a Claude Code plugin

Claude Code
/plugin marketplace add agent-data/job-search
/plugin install job-search@agent-data

Google Jobs (Apify)

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Only Google Jobs (Apify) 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

Neither one's marketplaces publish the settings it asks for.

What it can do: job-search · What it can do: Google Jobs (Apify) · 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