Ext Ops Panel
Open dashboard
Comparison

Pauhu EU Data vs io.github.jbechtel-97/dealflowpro

Pauhu EU Data is an MCP server published by pauhu.eu. 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-30. 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
MarketplacePauhu EU Dataio.github.jbechtel-97/dealflowpro
Official MCP Registry Listed
Version: 1.0.1
No figure published
Not marked · First seen
Listed
Version: 1.4.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.4.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

Pauhu EU Data vs io.github.jbechtel-97/dealflowpro
FactPauhu EU Dataio.github.jbechtel-97/dealflowpro
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub4
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)2026-10-19 (worse)2026-10-28 (better)
Where it runs (differs)Remote server (api.pauhu.eu/mcp)On your machine (dealflowpro-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/jbechtel-97/dealflowpro-mcp-server
Changes in the last 7 days (differs)02
First seen (differs)2026-10-192026-10-11
Endpoint at the last check (differs)Responded 3 days agono remote endpoint we check

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

Pauhu EU Data

In its own words, on Official MCP Registry:

Cited search (free daily allowance), citation checks, translation; EU data sets on annual licence

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

Pauhu EU Data As a remote MCP server

Claude Code
claude mcp add --transport http data https://api.pauhu.eu/mcp

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.

Only Pauhu EU Data has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of io.github.jbechtel-97/dealflowpro nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of Pauhu EU Data publish no settings it asks for, so we do not compare settings.

What it can do: Pauhu EU Data · 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.

Where the data comes from: how the catalog is built