REGON (Polish business register)

io.github.SmartMobileHouse由 GitHub 帳號 SmartMobileHouse 發布v0.2.3更新於 Nov 7, 2026

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

發布方自己的服務:Register.gy

概覽

AI 產生的概覽

依 NIP、REGON 或 KRS 查詢波蘭 GUS REGON 商業登記資料庫中的企業,並將結構化的登記資料回傳給助理。

可以做什麼
  • 依 NIP、REGON 或 KRS 查詢單一波蘭企業,取得名稱、REGON、地址與企業類型
  • 一次批次查詢最多 20 筆同一識別碼類型的實體,並列出未比對到的識別碼
  • 依 REGON 取得單一企業的詳細 REGON 報告
  • 列出可用的報告類型,並說明如何依企業類型挑選
  • 每筆回應都附來源區塊,標明登記資料庫、環境與擷取時間戳
適用情境
適合助理需要查核或補充波蘭公司資料的情境,例如核對合作對象的 NIP、解析 KRS 編號,或為盡職調查與開立發票流程取得官方登記細節。
執行需求
以 Python 套件形式透過 stdio 在本機執行,通常以 uvx 啟動。預設使用公開測試金鑰連線匿名的 GUS 測試資料庫,無需任何設定。若要取得即時資料,需向 GUS 申請免費的 BIR USER_KEY,並設定環境變數 REGON_API_KEY 與 REGON_ENV=prod;REGON_TIMEOUT 可設定 HTTP 逾時。需要能連線至 GUS 服務的網路。
安裝前請注意
測試環境回傳的實體資料很少或為空,有意義的結果需要正式版 USER_KEY。金鑰透過 REGON_API_KEY 環境變數傳入,應避免寫入共用設定檔。查詢會送往 GUS 登記服務,須遵守 GUS 使用條款與速率限制。資料屬於 GUS,引用時應註明擷取日期。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 REGON (Polish business register),將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

regon-mcp

A Model Context Protocol server that gives AI assistants clean, typed access to the Polish REGON business register (GUS BIR1). Look up any Polish company by NIP, REGON, or KRS and get back structured data — name, address, legal form, activity codes — without touching the underlying SOAP API.

The official GUS BIR1 API is a WCF SOAP service with WS-Addressing, MTOM multipart responses, an HTTP-header session token, and XML-nested-inside-XML result payloads. regon-mcp hides all of that behind a handful of simple tools.

Built and maintained by Smart Mobile House — secure AI implementation for enterprise.

Background and design notes: the regon-mcp write-up.

Tools

ToolDescription
search_by_nip(nip)Look up an entity by 10-digit NIP (tax id).
search_by_regon(regon)Look up an entity by 9- or 14-digit REGON.
search_by_krs(krs)Look up an entity by 10-digit KRS (court register).
search_bulk(identifiers, id_type)Look up up to 20 entities of one type at once.
get_full_report(regon, report_type)Fetch a detailed report for one entity.
list_report_types()List valid report names, with guidance on which to use.

Every response includes a source block that names the register (REGON / GUS), the environment, and a UTC retrieved_at timestamp — so downstream use can cite the data correctly, as GUS requires.

Quick start

No install needed — run it straight from the repo with uv:

bash
uvx --from git+https://github.com/SmartMobileHouse/regon-mcp regon-mcp

By default it uses the public test key against the anonymized GUS test database, so it runs with zero setup. For live data, request a free USER_KEY from [email protected] and set the environment variables below.

Use it in Claude Desktop / Claude Code

Add to your MCP config (e.g. claude_desktop_config.json or a project .mcp.json):

json
{  "mcpServers": {    "regon": {      "command": "uvx",      "args": ["--from", "git+https://github.com/SmartMobileHouse/regon-mcp", "regon-mcp"],      "env": {        "REGON_API_KEY": "your-user-key",        "REGON_ENV": "prod"      }    }  }}

During development, point it at a local checkout instead:

json
{  "mcpServers": {    "regon": {      "command": "uvx",      "args": ["--from", "/absolute/path/to/regon-mcp", "regon-mcp"],      "env": { "REGON_API_KEY": "abcde12345abcde12345" }    }  }}

Configuration

VariableDefaultDescription
REGON_API_KEYpublic test keyYour GUS BIR USER_KEY.
REGON_ENVtesttest (anonymized data) or prod (live data).
REGON_TIMEOUT30HTTP timeout in seconds.

Use REGON_ENV=prod only with a real USER_KEY; the test key works only against the test environment.

Development

bash
git clone https://github.com/SmartMobileHouse/regon-mcpcd regon-mcpuv sync                 # create the venv and install depsuv run pytest           # offline tests: validation, parsing, mocked client,                        # and an in-memory MCP tool-discovery smoke test.                        # (network tests are deselected by default)uv run regon-mcp        # run the server over stdio
# Live tests against the GUS endpoint (deselected unless opted in):REGON_RUN_NETWORK=1 uv run pytest -m network            # session lifecycle (test env)REGON_PROD_KEY=<your-key> uv run pytest -m network      # positive-control on live data

The client is a small hand-rolled SOAP layer over httpx (see src/regon_mcp/client.py) — no heavyweight SOAP stack, no runtime WSDL fetch.

Notes & limitations

  • The GUS test database is anonymized and returns little or no entity data. Meaningful results require a production USER_KEY with REGON_ENV=prod.
  • Respect the GUS terms of use and rate limits. This project is an independent open-source client and is not affiliated with or endorsed by GUS.
  • Data belongs to GUS. When you present it, cite REGON / GUS with the retrieval date (surfaced in every response's source block).

License

MIT © Smart Mobile House

來源:README.md,提交 c9ed771

工具

6

search_by_nip

Look up a Polish business entity by NIP (10-digit tax id). Returns basic registry data (name, REGON, address, entity type). Use the returned REGON with get_full_report() for the detailed record.

輸入參數nip必填

search_by_regon

Look up a Polish business entity by REGON (9- or 14-digit statistical id).

輸入參數regon必填

search_by_krs

Look up a Polish business entity by KRS (10-digit court-register number).

輸入參數krs必填

search_bulk

Look up up to 20 entities of the same identifier type in one call. id_type must be one of: "nip", "krs", "regon9", "regon14". The response adds `requested` (normalized inputs) and `unmatched` (requested ids with no returned row) so partial results are explicit. For KRS the service does not echo the KRS in search rows, so `unmatched` is null there.

輸入參數id_type必填identifiers必填

get_full_report

Fetch a detailed REGON report for one entity by REGON. Choose report_type from list_report_types(), based on the entity's `type` and `silo_id` returned by a search.

輸入參數regon必填report_type必填

list_report_types

List valid report_type values for get_full_report(), with guidance. These are the BIR1.1 report names. Picking the right report: - type "P" (legal person) -> BIR11OsPrawna - type "F" (natural person) -> by silo_id: 1 -> BIR11OsFizycznaDzialalnoscCeidg 2 -> BIR11OsFizycznaDzialalnoscRolnicza 3 -> BIR11OsFizycznaDzialalnoscPozostala 4 -> BIR11OsFizycznaDzialalnoscSkreslonaDo20141108 - local units (LP / LF) -> BIR11JednLokalnaOsPrawnej / ...OsFizycznej

無需輸入參數。

版本歷史

2
  1. v0.2.3最新Nov 4, 2026
  2. v0.2.2Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Register 整合