Ext Ops Panel
Open dashboard
Comparison

career-brand vs io.github.johnisanerd/linkedin-post-search

career-brand is a plugin bundle for AI coding tools published by asaferdman23. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.johnisanerd/linkedin-post-search is an MCP server published by johnisanerd. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
Marketplacecareer-brandio.github.johnisanerd/linkedin-post-search
Claude Code: claude-plugins-community Listed
Version: 0.3.0
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

career-brand vs io.github.johnisanerd/linkedin-post-search
Factcareer-brandio.github.johnisanerd/linkedin-post-search
Marketplaces that list it11
Stars (GitHub) (differs)5 (better)0 (worse)
Forks (GitHub)00
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
Hooks it runs (differs)1Not published
Parts of the bundle (differs)6Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/asaferdman23/career-brand-plugingithub.com/johnisanerd/apify-linkedin-post-search-api
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-03
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 47 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

career-brand

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

AI-powered personal branding and career strategy for LinkedIn. Two skills that work together: /brand — Scans your LinkedIn profile, learns your story, and helps you write posts that sound like you (not like AI). Creates monthly content calendars, brainstorms ideas from your recent work, and offers hook variations to choose from. Supports any language. /career — Career co-pilot that considers your full picture: job search, side projects, and unique background. Evaluates job offers, optimizes your LinkedIn profile, builds networking strategies, and preps you for interviews with stories from your real experience. Includes a career-advisor agent that ensures your content strategy aligns with your career goals. Works for engineers, product managers, founders, career changers, and anyone who deserves to be visible for the work they do.

io.github.johnisanerd/linkedin-post-search

In its own words, on Official MCP Registry:

Search public LinkedIn posts by keyword, name or hashtag, with engagement, via a hosted MCP server.

How to run each

career-brand As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install career-brand@claude-community

io.github.johnisanerd/linkedin-post-search

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 io.github.johnisanerd/linkedin-post-search 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: career-brand · What it can do: io.github.johnisanerd/linkedin-post-search · 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 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