Ext Ops Panel
Open dashboard
Comparison

io.github.jbechtel-97/dealflowpro vs BoringToolsKit

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)). BoringToolsKit is an MCP server published by roadtogideon222-byte. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-06. 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
Marketplaceio.github.jbechtel-97/dealflowproBoringToolsKit
Official MCP Registry Listed
Version: 1.4.0
Downloads/month (npm): 870
Downloads/week (npm): 326
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 1.4.0
Downloads/month (npm): 870
Downloads/week (npm): 326
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

io.github.jbechtel-97/dealflowpro vs BoringToolsKit
Factio.github.jbechtel-97/dealflowproBoringToolsKit
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)4 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-10-28Not published
Where it runs (differs)On your machine (dealflowpro-mcp)Remote server (boringtoolskit.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/jbechtel-97/dealflowpro-mcp-servergithub.com/roadtogideon222-byte/boringtoolskit
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-14
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 2 days ago returned HTTP 200

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

In its own words, on Official MCP Registry:

Multifamily real estate deal analysis — cap rate, DSCR, IRR, DFP Score, max offer price

BoringToolsKit

In its own words, on Official MCP Registry:

36 free private calculator tools for Claude. No accounts, no data leaves your session.

How to run each

io.github.jbechtel-97/dealflowpro As a local MCP server: npm package

Claude Code
claude mcp add --env "DFP_API_KEY=<YOUR_DFP_API_KEY>" --transport stdio dealflowpro -- npx -y dealflowpro-mcp

Requires: DFP_API_KEY (secret)

BoringToolsKit As a remote MCP server

Claude Code
claude mcp add --transport http boringtoolskit https://boringtoolskit.com/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only BoringToolsKit 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

The marketplaces of BoringToolsKit 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: BoringToolsKit · 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.

Where the data comes from: how the catalog is built