Regon Pl MCP server

@pipeworx/regon-pl

Polish business register (REGON / BIR1.1) — resolve any Polish company by NIP, REGON or KRS number to its registered name, legal address and entity type, from Statistics Poland's official register.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

• regonsearchnip({ nip, environment, _apiKey }) — by tax identification number.
• regonsearchregon({ regon, environment, _apiKey }) — by 9- or 14-digit REGON statistical number.
• regonsearchkrs({ krs, environment, _apiKey }) — by National Court Register number.

All three return the registered name, the other two identifiers, entity type (legal person / sole trader / local unit), voivodeship, county, municipality, locality, postcode and registered address.

Auth

Platform key (PLATFORMREGONKEY) with BYO override via ?apiKey=, plus a credential-free test path**.

key. Register free at ; GUS issues a 20-character user key.

• environment: "production" (default) — the live register. Requires an API

publishes in its documentation. Needs no credential and genuinely answers, but from a small fixed fixture database (addresses read "ul. Test-Wilcza"). Use it to check the response shape, never for a fact about a real company. Every response from it carries a disclaimer field saying so.

• environment: "test" — GUS's own public test service with the test key GUS

Data sources

• — production BIR1.1.
• — test BIR1.1.

Traps

the user key for a session id, then the search carries it.

• SOAP 1.2 over MTOM, not REST. Two calls per query: Zaloguj exchanges

Put it in the envelope and the service authenticates you as nobody and returns an empty result with no error.

• The session id goes in an HTTP sid header, not in the SOAP envelope.

whose only fields are ErrorCode 4 and ErrorMessageEn "No data found for the specified search criteria". Parsed naively that is one result with every field null — a textbook silent zero. This pack detects ErrorCode and reports found: false with the upstream message.

• A no-match is not an empty document. It is a populated record

an HTTP error. The pack raises on it explicitly.

• An unrecognised user key is reported as an empty ZalogujResult, not as

the SOAP result element — it needs unwrapping twice.

• Responses are MIME-multipart with the payload as an XML-escaped string inside

• Sessions are cached in worker memory for 30 minutes (upstream allows ~60).

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "regon-pl": {
      "url": "https://gateway.pipeworx.io/regon-pl/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/regon-pl/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Shortened. The full README is on GitHub.