vendor-directory-builder vs io.github.jbechtel-97/dealflowpro
vendor-directory-builder is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑03.
vendor-directory-builder is a plugin bundle for AI coding tools published by DataSift. No marketplace we read lists it any more. 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-11-13. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace datasift-ty-personal/siftstack | Removed on 2026-11-03 Version: not stated Forks (GitHub): 23 Stars (GitHub): 23 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.0 Downloads/month (npm): 870 Downloads/week (npm): 326 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.4.0 Downloads/month (npm): 870 Downloads/week (npm): 326 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 | vendor-directory-builderno longer listed · | io.github.jbechtel-97/dealflowpro |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 23 | 4 |
| Forks (GitHub) (differs) | 23 | 0 |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (dealflowpro-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/datasift-ty-personal/siftstack | github.com/jbechtel-97/dealflowpro-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of vendor-directory-builder
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
servicegraph co.servicegraph.mcp/servicegraph
Datasets for founders: directories, newsletters, and agencies, with metrics attached.
-
Find local businesses, enrich them with emails and socials, and run lead pipelines from your AI.
-
Find local businesses with real emails and run AI-written outreach to them, from your AI chat.
-
Web scraping and AI sales workspace with scoped CRM, scraping, knowledge and sales workflow tools.
-
Local business leads and website intelligence for AI agents: lead lists, contacts, tracking, SEO and
-
MCP-native co-founder directory your AI agent searches, screening inbound pitches for you.
What each says it does
vendor-directory-builder
Build a vetted, filterable directory of local service providers (general contractors, subcontractors, trade crews, or any vendors) for a target market by mining a community source (a Facebook group, forum, subreddit,...
io.github.jbechtel-97/dealflowpro
Multifamily real estate deal analysis — cap rate, DSCR, IRR, DFP Score, max offer price
How to run each
vendor-directory-builder
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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
The marketplaces of vendor-directory-builder publish no settings it asks for, so we do not compare settings.
What it can do: vendor-directory-builder · What it can do: io.github.jbechtel-97/dealflowpro · 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. 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.