brreg-mcp
Related Servers
Alternatives to brreg-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables interaction with the Norwegian Business Registry (Brønnøysundregistrene) API to search and retrieve detailed information about Norwegian companies, subunits, roles, organization forms, municipalities, and NACE industry codes.184 npm1MIT
- AlicenseBqualityDmaintenanceEnables comprehensive access to the Norwegian Business Registry API for querying company information, board members, subsidiaries, organizational data, and voluntary organizations. Provides real-time access to over 1 million registered Norwegian entities with detailed corporate structure and governance data.154 npm8MIT
- AlicenseAqualityDmaintenanceEnables AI agents to search and retrieve Norwegian company data from the Brønnøysund Register Centre's open API, including company details, roles, and subunits.54 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides access to Norway's official business registry for searching companies, looking up organizational details, and identifying company roles and sub-units. It utilizes data from Brønnøysundregistrene to enable detailed queries by industry, municipality, or organization number.5 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceProvides comprehensive Norwegian business intelligence through Brønnøysund and Statistics Norway APIs, enabling company search, financial analysis, ownership mapping, market research, and automated financial data extraction.-
- AlicenseNot gradedqualityBmaintenanceMCP server for querying the Norwegian Brønnøysundregistrene business register, including companies, roles, subunits, and annual accounts, with built-in guards against common data traps like retired NACE codes and withheld employee counts.6 npmMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: lookup by ID, search by name/filters, retrieve roles, search subunits, and get recent updates. The descriptions explicitly differentiate between main entities (enheter) and subunits (underenheter), eliminating any overlap confusion.
All tool names follow a consistent verb_noun pattern (lookup_company, search_companies, get_company_roles, search_subunits, get_recent_updates) using snake_case. Verb choices are appropriate and parallel, with minor pluralization differences but no stylistic inconsistency.
With 5 tools, the set is well-scoped for a read-only business registry API. Each tool covers a distinct need (lookup, search, roles, subunits, updates) without superfluous additions, fitting comfortably in the ideal 3-15 range.
The tool surface comprehensively covers the core operations for the Norwegian business register: retrieving a specific entity, searching for entities, accessing roles, exploring subunits, and monitoring updates. Given the read-only nature of the registry, there are no obvious gaps in lifecycle coverage.