Ext Ops Panel
Open dashboard
Comparison

Job Postings Aggregator vs OpenHire · 哨兵

Job Postings Aggregator is an MCP server published by fernandoguiraud16-coder. Marketplaces we read that list it: 1 (Official MCP Registry). OpenHire · 哨兵 is an MCP server published by gzchenhao. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-06. 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 Postings AggregatorOpenHire · 哨兵
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.8.62
Downloads/month (PyPI): 1 890
Downloads/week (PyPI): 3 229
Forks (GitHub): 0
Stars (GitHub): 14
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 Postings Aggregator vs OpenHire · 哨兵
FactJob Postings AggregatorOpenHire · 哨兵
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)14 (better)
Forks (GitHub)00
Last release (differs)Not published2026-11-06
Where it runs (differs)Remote server (mcp.apify.com)On your machine (openhire)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Licence (differs)Not statedMIT
Repository (differs)github.com/fernandoguiraud16-coder/data-toolsgithub.com/gzchenhao/openhire
Changes in the last 7 days (differs)011
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)Responded 27 h ago, requires authenticationno remote endpoint we check

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 Postings Aggregator

In its own words, on Official MCP Registry:

Jobs from LinkedIn, Indeed and company sites via Google Jobs: salaries, apply links, alerts.

OpenHire · 哨兵

In its own words, on Official MCP Registry:

Jobs with the employer's real posting date, from employers' own ATS. HR family. Résumé stays local.

How to run each

Job Postings Aggregator

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

OpenHire · 哨兵 As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio openhire -- uvx openhire serve

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

Only Job Postings Aggregator 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

The marketplaces of Job Postings Aggregator publish no settings it asks for, so we do not compare settings.

What it can do: Job Postings Aggregator · What it can do: OpenHire · 哨兵 · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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