Ext Ops Panel
Open dashboard
Comparison

job-apply vs TryCatchJob

job-apply is a plugin bundle for AI coding tools published by Jeremy Watt. Marketplaces we read that list it: 1 (Community GitHub marketplaces). TryCatchJob is an MCP server published by trycatchjob.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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-applyTryCatchJob
Community marketplace neonwatty/job-apply-plugin Listed
Version: not stated
Forks (GitHub): 28
Stars (GitHub): 138
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.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-apply vs TryCatchJob
Factjob-applyTryCatchJob
Marketplaces that list it11
Stars (GitHub) (differs)138No figure on GitHub
Forks (GitHub) (differs)28No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (trycatchjob.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/neonwatty/job-apply-pluginNot stated
Changes in the last 7 days (differs)12
First seen (differs)2026-10-302026-11-04
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 38 h ago returned HTTP 401

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-apply

In its own words, on Community GitHub marketplaces:

AI-powered job application assistant for Claude Code and Codex covering LinkedIn, Greenhouse, Ashby, Lever, Rippling, and Workday

TryCatchJob

In its own words, on Official MCP Registry:

Track job applications: find the ones to follow up on, add jobs, update status, notes and steps.

How to run each

job-apply As a Claude Code plugin

Claude Code
/plugin marketplace add neonwatty/job-apply-plugin
/plugin install job-apply@neonwatty-plugins

TryCatchJob As a remote MCP server

Claude Code
claude mcp add --transport http trycatchjob https://trycatchjob.com/mcp

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

Only TryCatchJob 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-apply · What it can do: TryCatchJob · 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