Ext Ops Panel
Open dashboard
Comparison

OpenHire · 哨兵 vs LinkedIn Posts

OpenHire · 哨兵 is an MCP server published by gzchenhao. Marketplaces we read that list it: 1 (Official MCP Registry). LinkedIn Posts is an MCP server published by saulius876-lgtm. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
MarketplaceOpenHire · 哨兵LinkedIn Posts
Official MCP Registry Listed
Version: 0.8.32
Downloads/month (PyPI): 1 890
Downloads/week (PyPI): 1 178
Forks (GitHub): 0
Stars (GitHub): 14
Not marked · First seen
Listed
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

OpenHire · 哨兵 vs LinkedIn Posts
FactOpenHire · 哨兵LinkedIn Posts
Marketplaces that list it11
Stars (GitHub) (differs)14No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)2026-10-29Not published
Where it runs (differs)On your machine (openhire)Remote server (mcp.apify.com)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Licence (differs)MITNot stated
Repository (differs)github.com/gzchenhao/openhireNot stated
Changes in the last 7 days (differs)100
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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

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.

LinkedIn Posts

In its own words, on Official MCP Registry:

LinkedIn posts with text, author, date, reactions, top comments, media from links or company pages.

How to run each

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

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

LinkedIn Posts

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

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

Only LinkedIn Posts 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 LinkedIn Posts publish no settings it asks for, so we do not compare settings.

What it can do: OpenHire · 哨兵 · What it can do: LinkedIn Posts · 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