HirePulse tools vs io.github.jbechtel-97/dealflowpro
HirePulse tools is an MCP server published by edtool79-collab. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.jbechtel-97/dealflowpro is an MCP server published by jbechtel-97. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-24. 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
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.3.0 Downloads/month (npm): 630 Downloads/week (npm): 377 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.3.0 Downloads/month (npm): 630 Downloads/week (npm): 377 Forks (GitHub): 0 Stars (GitHub): 4 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
| Fact | HirePulse tools | io.github.jbechtel-97/dealflowpro |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 4 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-18 (worse) | 2026-10-21 (better) |
| Where it runs (differs) | On your machine (hirepulse-tools) | On your machine (dealflowpro-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/edtool79-collab/hirepulse-open-source | github.com/jbechtel-97/dealflowpro-mcp-server |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-17 | 2026-10-11 |
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
HirePulse tools
Apify tools for products, Google ads, company signals, jobs, keywords, SEO and YouTube transcripts.
io.github.jbechtel-97/dealflowpro
Multifamily real estate deal analysis — cap rate, DSCR, IRR, DFP Score, max offer price
How to run each
HirePulse tools As a local MCP server: PyPI package
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio hirepulse-open-source -- uvx --from "hirepulse-tools[mcp]==0.3.0" hirepulse-tools hirepulse-mcp
Requires: APIFY_TOKEN (secret)
io.github.jbechtel-97/dealflowpro As a local MCP server: npm package
claude mcp add --env "DFP_API_KEY=<YOUR_DFP_API_KEY>" --transport stdio dealflowpro -- npx -y dealflowpro-mcp
Requires: DFP_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
Only HirePulse tools asks for
APIFY_TOKEN (secret)
Only io.github.jbechtel-97/dealflowpro asks for
DFP_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: HirePulse tools · What it can do: io.github.jbechtel-97/dealflowpro · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.