Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.hellosverre/brreg

NPM · BRREG-MCP · SCANNED SEP 20

MCP server for Norway's Brønnøysund business registry — lookup, search, roles.

Available components

0 this week 82 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 742 tokens (~148/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.hellosverre/brreg MCP server?

io.github.hellosverre/brreg runs locally as an npm package, launched with npx -y brreg-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · brreg-mcp

# add to Claude Code
claude mcp add hellosverre-brreg -- npx -y brreg-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "hellosverre-brreg": {
      "command": "npx",
      "args": [
        "-y",
        "brreg-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hellosverre-brreg": {
      "command": "npx",
      "args": [
        "-y",
        "brreg-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add hellosverre-brreg -- npx -y brreg-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hellosverre-brreg": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "brreg-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hellosverre-brreg --command npx --arg -y --arg brreg-mcp
# ~/.hermes/config.yaml
mcp_servers:
  hellosverre-brreg:
    command: "npx"
    args: ["-y", "brreg-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hellosverre-brreg": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "brreg-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add hellosverre-brreg -t stdio -c npx -a -y brreg-mcp
// mcp.json
{
  "mcpServers": {
    "hellosverre-brreg": {
      "command": "npx",
      "args": [
        "-y",
        "brreg-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 19 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 17 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 16 Sept 26 −3
    • Security disclosure: fail → unverified functional
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1
    • Security disclosure: unverified → fail functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/brreg-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~742 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_company_roles ~93

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

NameTypeReqDescription
orgnrstringyes9-digit Norwegian organization number

No output schema declared.

No examples provided.

get_recent_updates ~124

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.

NameTypeReqDescription
datostringISO-8601 timestamp — return updates from this point onward (e.g. '2026-04-20T00:00:00Z')
oppdateringsidintegerContinue from a specific update id (pagination cursor)
sizeinteger

No output schema declared.

No examples provided.

lookup_company ~113

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.

NameTypeReqDescription
orgnrstringyes9-digit Norwegian organization number (organisasjonsnummer), e.g. '923609016'

No output schema declared.

No examples provided.

search_companies ~266

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.

NameTypeReqDescription
kommunenummerstring4-digit municipality number (kommunenummer) to filter by location
konkursbooleanFilter by bankruptcy status (true = only bankrupt, false = only non-bankrupt)
naeringskodestringNACE industry code filter (e.g. '62.010' for computer programming)
navnstringCompany name or substring (case-insensitive)
organisasjonsformstringFilter by organization form code, e.g. 'AS' (aksjeselskap), 'ENK' (enkeltpersonforetak), 'ASA', 'DA', 'NUF'
pageintegerPage number (0-indexed, default 0)
postnummerstring4-digit postal code filter
registrertIMvaregisteretbooleanFilter to only VAT-registered companies
sizeintegerResults per page (1-100, default 20)

No output schema declared.

No examples provided.

search_subunits ~146

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.

NameTypeReqDescription
kommunenummerstring4-digit municipality number
naeringskodestringNACE industry code
navnstringSubunit name or substring
overordnetEnhetstring9-digit orgnr of the parent entity to list all its subunits
pageinteger
sizeinteger

No output schema declared.

No examples provided.

Common questions

What is the io.github.hellosverre/brreg MCP server?

io.github.hellosverre/brreg is an MCP server listed in the public MCP registry as io.github.hellosverre/brreg. MCP server for Norway's Brønnøysund business registry, lookup, search, roles. This page covers its npm package (brreg-mcp).

Is the io.github.hellosverre/brreg MCP server safe to use?

io.github.hellosverre/brreg scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.hellosverre/brreg MCP server expose?

io.github.hellosverre/brreg exposes 5 tools: lookup_company, search_companies, get_company_roles, search_subunits, get_recent_updates. Their descriptions and schemas cost roughly 742 tokens of context every time the server is loaded.

Is the io.github.hellosverre/brreg MCP server still maintained?

io.github.hellosverre/brreg is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.hellosverre/brreg MCP server under?

io.github.hellosverre/brreg declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.