Skip to main content
Glama

Server Details

Brønnøysund Register Centre (BRREG) MCP — Norway's official business register. Enhetsregisteret…

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-brreg-no
GitHub Stars
0
Server Listing
mcp-brreg-no
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 50 tools

Disambiguation2/5

Several clusters are genuinely hard to tell apart: ask_pipeworx vs ask_pipeworx_beta (the description itself says they currently behave identically), ask_pipeworx vs ask_pipeworx_grounded vs deep_research vs validate_claim vs discover_tools vs suggest_questions all answer 'route my question to data', and archive_compare vs archive_evidence overlap until the final sentence. Entity tools also blur (resolve_entity vs company_register_search vs entity_profile vs company_facts vs compare_entities vs recent_changes), and Polymarket has ~10 tools (edges/edge_tracker/arbitrage/fill_risk/bet_research/calibration/updown_*) whose boundaries only become clear after reading very long descriptions. Descriptions do heavy lifting, but an agent choosing blind will misfire regularly.

Naming Consistency3/5

Everything is snake_case, which is good, but the convention is mixed: verb_noun (get_entity, search_entities, resolve_entity, compare_entities, validate_claim) alongside bare noun phrases (company_facts, entity_profile, prediction_calibration, polymarket_edges, kalshi_weather_edge) and bare verbs (remember, recall, forget, subscribe, unsubscribe). Prefixed families (get_*/search_*/polymarket_*/updown_*) are readable, but the same verb-object grammar is not applied consistently across the catalog.

Tool Count1/5

50 tools is at the extreme end and is a severe mismatch with the apparent scope of a server named 'Brreg No' (Norwegian business registry), which would need roughly six tools. The surface sprawls into prediction-market arbitrage, SEC/XBRL facts, npm dependency scanning, LLM visibility probing, agent memory, subscriptions and web archive diffing — a catalog, not a toolset, and far past what an agent can hold in context and choose from reliably.

Completeness3/5

For the named domain the registry coverage is actually complete: search_entities, get_entity, get_sub_entity, search_sub_entities, get_accounts and get_roles cover Norwegian entity lookup, branches, filings and roles with no dead ends (read-only is correct for a register). But across the 50-tool surface coverage is uneven — deep in some verticals (Polymarket, entity resolution) and shallow or single-tool in others (one npm tool, one AI-visibility pair, no cross-domain glue), so agents will still hit gaps outside the registry core.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for the Norwegian Central Coordinating Register for Legal Entities (Enhetsregisteret), providing tools to search companies, get full register records, list recent registrations, and retrieve registered roles.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Nordic company registries. Verify companies, check board members, signing authority, and financial data across Norway, Denmark, Finland, and Sweden using official public APIs. 23 tools covering search, details, roles, and batch lookups.
      19
      14
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.