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 集成