brreg-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sok_foretakA | Søk etter norske foretak i Enhetsregisteret. Kan filtrere på navn, næringskode, kommunenummer, organisasjonsform, og mer. |
| hent_foretakA | Hent detaljert informasjon om et norsk foretak basert på organisasjonsnummer. |
| hent_rollerA | Hent roller (styremedlemmer, daglig leder, revisor, etc.) for et norsk foretak. |
| sok_underenheterA | Søk etter underenheter (avdelinger, filialer) i Enhetsregisteret. |
| hent_underenhetA | Hent detaljert informasjon om en underenhet basert på organisasjonsnummer. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: search vs. retrieve for both main entities and sub-units, and roles retrieval for a specific entity. There is no overlap or ambiguity among the five tools.
All tool names follow the same Norwegian verb_noun pattern: 'sok_' for searching and 'hent_' for retrieving, with the entity type appended. This creates a predictable and coherent naming convention across the entire set.
Five tools is a well-scoped count for a business registry lookup server, covering the two core entity types (foretak and underenheter) with both search and detail retrieval, plus a roles endpoint. It feels complete without being bloated.
The tool set covers the essential read-only operations for the domain: searching and retrieving main entities and sub-units, and fetching roles. A minor gap is the lack of a direct endpoint to list all sub-units for a given parent company, but this can be worked around via the search tool by filtering on the parent's organization number.