Ext Ops Panel
Open dashboard
Comparison

findem-studio vs reapx jobs - listings from Greenhouse, Workable, Reed and more

findem-studio is a plugin bundle for AI coding tools published by findemdev. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). reapx jobs - listings from Greenhouse, Workable, Reed and more is an MCP server published by reapx.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplacefindem-studioreapx jobs - listings from Greenhouse, Workable, Reed and more
Claude Code: claude-plugins-community Listed
Version: 9115be6
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed, marked deprecated
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

findem-studio vs reapx jobs - listings from Greenhouse, Workable, Reed and more
Factfindem-studioreapx jobs - listings from Greenhouse, Workable, Reed and more
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No 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
LicenceNot statedNot stated
Repository (differs)github.com/findemdev/findem-studio-claude-pluginNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 23 h 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

findem-studio

In its own words, on Claude Code: claude-plugins-community:

Findem Studio plugin for talent intelligence — 3 remote MCP connectors with OAuth, comprehensive reviewer runbook.

reapx jobs - listings from Greenhouse, Workable, Reed and more

In its own words, on Official MCP Registry:

Scrape job listings from Greenhouse, Workable, Reed, RemoteOK and other boards. Pay per row.

How to run each

findem-studio As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install findem-studio@claude-community

reapx jobs - listings from Greenhouse, Workable, Reed and more

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

Requires: Authorization header

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

Only reapx jobs - listings from Greenhouse, Workable, Reed and more 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: findem-studio · What it can do: reapx jobs - listings from Greenhouse, Workable, Reed and more · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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