Ext Ops Panel
Open dashboard
Comparison

vibe-prospecting vs HireHeat: Hiring Signals & Company Job Postings by Domain

vibe-prospecting is a plugin bundle for AI coding tools published by vibeprospecting.ai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). HireHeat: Hiring Signals & Company Job Postings by Domain is an MCP server published by shawmena-dotcom. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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
Marketplacevibe-prospectingHireHeat: Hiring Signals & Company Job Postings by Domain
Community marketplace davepoon/buildwithclaude Listed
Version: 0.1.56
Forks (GitHub): 664
Stars (GitHub): 3 691
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
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

vibe-prospecting vs HireHeat: Hiring Signals & Company Job Postings by Domain
Factvibe-prospectingHireHeat: Hiring Signals & Company Job Postings by Domain
Marketplaces that list it11
Stars (GitHub) (differs)3 691No figure on GitHub
Forks (GitHub) (differs)664No 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
Licence (differs)MITNot stated
Repository (differs)github.com/davepoon/buildwithclaudegithub.com/shawmena-dotcom/product-factory
Changes in the last 7 days00
First seen (differs)2026-10-152026-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

vibe-prospecting

In its own words, on Community GitHub marketplaces:

Power your chat with live B2B data to create lead lists, research companies, enrich contacts, personalize outreach, and inspect business signals, tech stacks, events, and website changes. 150M+ businesses and 800M+ professionals via the Explorium MCP.

HireHeat: Hiring Signals & Company Job Postings by Domain

In its own words, on Official MCP Registry:

HireHeat: who's hiring? Open and new roles per company domain by function, seniority, location.

How to run each

vibe-prospecting As a Claude Code plugin

Claude Code
/plugin marketplace add davepoon/buildwithclaude
/plugin install vibe-prospecting@buildwithclaude

HireHeat: Hiring Signals & Company Job Postings by Domain

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 HireHeat: Hiring Signals & Company Job Postings by Domain 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: vibe-prospecting · What it can do: HireHeat: Hiring Signals & Company Job Postings by Domain · Compare two other plugins

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