mcp-brreg
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 |
|---|---|
| search_companiesA | Search Enhetsregisteret by name, industry code, municipality or legal form. Returns registered companies with address, industry and contact details where the register has them. |
| get_companyA | Full register record for a single Norwegian organisation number. |
| list_recent_registrationsA | Companies entered into the register within a recent date window, optionally filtered by municipality and legal form. Useful for tracking new business activity in an area. |
| get_rolesA | Registered roles for a company — board members, chair, general manager and similar, as published in the public register. |
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 4 tools
Each tool targets a distinct aspect of the register: searching by criteria, fetching full company details, listing recent registrations, and retrieving roles. There is no functional overlap; search_companies and list_recent_registrations differ by query type and purpose.
All tool names follow a consistent verb_noun pattern: search_companies, get_company, list_recent_registrations, get_roles. The verbs are action-oriented and the nouns are clear, making the pattern predictable and easy to infer.
With 4 tools, the server is well-scoped for a public company register API. Each tool serves a distinct common use case without unnecessary bloat, and the count is neither too sparse nor overwhelming.
The tool set covers the essential read operations for the domain: discovery (search and recent registrations), detailed lookup (get_company), and related structured data (get_roles). Since the register is public and read-only, no create/update/delete is expected. The surface is complete for typical consumer needs.