Ext Ops Panel
Open dashboard
Comparison

token-cost vs io.github.jbechtel-97/dealflowpro

token-cost is a plugin bundle for AI coding tools published by EvilFreelancer. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-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

Where each is published
Marketplacetoken-costio.github.jbechtel-97/dealflowpro
Community marketplace evilfreelancer/rpa-skills Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.9
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.2.9
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

token-cost vs io.github.jbechtel-97/dealflowpro
Facttoken-costio.github.jbechtel-97/dealflowpro
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)4 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-16
Where it runs (differs)Installs as a plugin bundleOn your machine (dealflowpro-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceMITMIT
Repository (differs)github.com/evilfreelancer/token-costgithub.com/jbechtel-97/dealflowpro-mcp-server
Changes in the last 7 days22
First seen (differs)2026-10-182026-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

token-cost

In its own words, on Community GitHub marketplaces:

Estimate the floor (self-) cost of a self-hosted LLM token: electricity + hardware amortization, measured on the server. Not the market API price.

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

How to run each

token-cost As a Claude Code plugin

Claude Code
/plugin marketplace add evilfreelancer/rpa-skills
/plugin install token-cost@rpa-skills

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)

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 token-cost publish no settings it asks for, so we do not compare settings.

What it can do: token-cost · 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.

Where the data comes from: how the catalog is built