Skip to main content
Glama
SmartMobileHouse

regon-mcp

by SmartMobileHouse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
REGON_ENVNoEither 'test' (anonymized data) or 'prod' (live data).test
REGON_API_KEYNoYour GUS BIR USER_KEY.public test key
REGON_TIMEOUTNoHTTP timeout in seconds.30

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_by_nipA

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.
search_by_regonA

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

search_by_krsA

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

search_bulkA

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.
get_full_reportA

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.
list_report_typesA

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

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a distinct, well-defined purpose: three searches by specific identifiers (REGON, NIP, KRS), a bulk search, a detailed report fetcher, and a report type lister. There is no overlap or ambiguity between tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case: search_by_regon, search_by_nip, search_by_krs, search_bulk, get_full_report, list_report_types. The naming is predictable and uniform.

Tool Count5/5

Six tools is well-scoped for a registry lookup service. Each tool is necessary and covers a core function without unnecessary extras or missing essential operations.

Completeness5/5

The tool set fully covers the domain of Polish business registry lookups: searching by all major identifiers, bulk lookup, and obtaining detailed reports. The list_report_types tool ensures users can correctly choose report types, and the flow from search to report is well-supported.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources