Ext Ops Panel
Open dashboard
Comparison

REGON (Polish business register) vs pl.nipregon/nipregon

REGON (Polish business register) is an MCP server published by SmartMobileHouse. Marketplaces we read that list it: 1 (Official MCP Registry). pl.nipregon/nipregon is an MCP server published by nipregon.pl. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
MarketplaceREGON (Polish business register)pl.nipregon/nipregon
Official MCP Registry Listed
Version: 0.2.3
Downloads/month (PyPI): 100
Downloads/week (PyPI): 30
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

REGON (Polish business register) vs pl.nipregon/nipregon
FactREGON (Polish business register)pl.nipregon/nipregon
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-11-04Not published
Where it runs (differs)On your machine (regon-mcp)Remote server (api.nipregon.pl/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/smartmobilehouse/regon-mcpgithub.com/amr-dev-ps/nipregon-mcp
Changes in the last 7 days (differs)10
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 4 days ago returned HTTP 502

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

REGON (Polish business register)

In its own words, on Official MCP Registry:

Look up Polish businesses in the GUS REGON register (BIR1) by NIP, REGON, or KRS.

pl.nipregon/nipregon

In its own words, on Official MCP Registry:

Polish company registry: 4.4M firms, KRS/REGON data, VAT white list checks, financial statements

How to run each

REGON (Polish business register) As a local MCP server: PyPI package

Claude Code
claude mcp add --env "REGON_API_KEY=<YOUR_REGON_API_KEY>" --transport stdio regon-mcp -- uvx regon-mcp

Requires: REGON_API_KEY (secret)

pl.nipregon/nipregon As a remote MCP server

Claude Code
claude mcp add --transport http nipregon https://api.nipregon.pl/mcp

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

Only pl.nipregon/nipregon 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 pl.nipregon/nipregon publish no settings it asks for, so we do not compare settings.

What it can do: REGON (Polish business register) · What it can do: pl.nipregon/nipregon · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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