Ext Ops Panel
Open dashboard
Comparison

job-search vs Trackly CLI

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). Trackly CLI is an MCP server published by kevinastuhuaman. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-24. 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-searchTrackly CLI
Community marketplace agent-data/job-search Listed
Version: 0.9.0
Forks (GitHub): 4
Stars (GitHub): 56
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed, marked deprecated
Version: 0.1.10
Downloads/month (npm): 1 767
Downloads/week (npm): 130
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.22.2
Downloads/month (npm): 1 767
Downloads/week (npm): 130
Forks (GitHub): 0
Stars (GitHub): 3
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 Trackly CLI
Factjob-searchTrackly CLI
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)56 (better)3 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last release (differs)Not published2026-10-24
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedstdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)7Not a bundle
LicenceMITMIT
Repository (differs)github.com/agent-data/job-searchgithub.com/kevinastuhuaman/trackly-cli
Changes in the last 7 days (differs)010
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

job-search

In its own words, on Community GitHub marketplaces:

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

Trackly CLI

In its own words, on Official MCP Registry:

Job tracking CLI + MCP server for AI agents. 99K+ jobs, 775+ companies.

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

Trackly CLI As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio trackly -- npx -y trackly-cli mcp

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

Only Trackly CLI 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: Trackly CLI · 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. Package data comes from the public npm registry (registry.npmjs.org). 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