Ext Ops Panel
Open dashboard
Comparison

findem-studio vs HireLayer

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). HireLayer is an MCP server published by hirelayer.co. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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-studioHireLayer
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
Version: 1.1.1
Downloads/month (npm): 97
Downloads/week (npm): 97
Forks (GitHub): 0
Stars (GitHub): 0
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 HireLayer
Factfindem-studioHireLayer
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (hirelayer.co/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/findemdev/findem-studio-claude-plugingithub.com/hirelayer/hirelayer-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

HireLayer

In its own words, on Official MCP Registry:

Resume and CV parsing, candidate matching and ranking for recruiting and ATS AI agents.

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

HireLayer As a remote MCP server

Claude Code
claude mcp add --transport http hirelayer https://hirelayer.co/mcp

Requires: HIRELAYER_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 findem-studio publish no settings it asks for, so we do not compare settings.

What it can do: findem-studio · What it can do: HireLayer · 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