MCP server for Brønnøysund Register Centre — Norwegian business registry lookup for Claude Code
Five tools with complete schemas and strong descriptions (avg 180 chars, well above 10-char minimum). All parameters typed and described. Tool names follow verb_noun pattern (lookup_, search_, get_). Schemas use Zod with proper constraints (min/max, enums via descriptions). Error handling returns actionable messages with validation feedback. Main gaps: no output schema documentation, no tool annotations (readOnlyHint), no pagination metadata (total count, next_cursor) in responses, and descriptions lack explicit 'when to use' guidance. Composition is clean, each tool has one responsibility. No security issues detected (read-only operations, no secrets in params).
Retrieves all registered roles — board members (styre), CEO (daglig leder), chair (styreleder), auditor (revisor), sole proprietor (innehaver), etc. — for a Norwegian company. Returns structured role groups with person or entity role-holders. Does NOT include personal identification numbers (that requires Maskinporten auth).
Fetches a feed of entities (companies) that were recently updated in the Norwegian business registry. Useful for monitoring changes to specific companies or watching for new registrations / status changes. Each update references the changed entity by orgnr along with the change type and timestamp.
Retrieves full details of a Norwegian business entity from the Brønnøysund Register Centre (Enhetsregisteret) by its 9-digit organization number. Returns name, address, industry (NACE) codes, organization form, employee count, VAT registration status, bankruptcy status, foundation date, and more. Use this when the user provides or asks about a specific Norwegian orgnr.
Searches the Norwegian business registry (Enhetsregisteret) by name and optional filters. Returns a paginated list of matching entities. Use this when the user wants to find a company by name, or filter by municipality, industry code, organization form, or registration status.
Output schemas not documented. LLMs cannot infer what fields to expect from responses, forcing them to guess at downstream tool parameters and risk broken chains.
Pagination responses lack total count and next_cursor. search_companies and search_subunits accept page/size but responses do not indicate whether more results exist, forcing agents to guess or make extra calls.
Tool descriptions lack explicit 'when to use' guidance. E.g., lookup_company vs search_companies distinction is clear, but get_recent_updates does not explain when to call it vs polling individual companies.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
Searches subunits (underenheter — branch offices, departments, production sites) in the Norwegian business registry. Typically used to find all branches of a parent company, or to locate subunits in a specific municipality. A subunit shares the parent's organization but has its own orgnr for reporting purposes.
No tool annotations (readOnlyHint, idempotentHint). All tools are read-only and idempotent, but this is not declared in the schema, forcing LLMs to infer safety from descriptions.
Error messages are actionable but do not suggest recovery steps. E.g., 'No company found for orgnr' could suggest 'Try search_companies() with the company name instead.'