io.github.jbechtel-97/dealflowpro vs Batch Sanctions Screening
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)). Batch Sanctions Screening is an MCP server published by pcp183. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  io.github.jbechtel-97/dealflowpro | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.9 Downloads/month (npm): 630 Downloads/week (npm): 377 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 0.2.0 No figure published Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.2.9 Downloads/month (npm): 630 Downloads/week (npm): 377 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Not listed |
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 | io.github.jbechtel-97/dealflowpro | Batch Sanctions Screening |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 4 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-16 (worse) | 2026-10-17 (better) |
| Where it runs (differs) | On your machine (dealflowpro-mcp) | Remote server (sanctions-batch-production.up.railway.app/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/jbechtel-97/dealflowpro-mcp-server | github.com/pcp183/sanctions-batch |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-16 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
io.github.jbechtel-97/dealflowpro
Multifamily real estate deal analysis — cap rate, DSCR, IRR, DFP Score, max offer price
Batch Sanctions Screening
Screen up to 100 names vs sanctions and US export lists. $0.50/batch via x402.
How to run each
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-mcpRequires: DFP_API_KEY (secret)
Batch Sanctions Screening As a remote MCP server
claude mcp add --transport http sanctions-batch https://sanctions-batch-production.up.railway.app/mcpCommands 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 Batch Sanctions Screening publish no settings it asks for, so we do not compare settings.
What it can do: io.github.jbechtel-97/dealflowpro · What it can do: Batch Sanctions Screening · 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.