BRREG Norway Business Register MCP Server

https://gateway.pipeworx.io/brreg-no/mcp Remote v0.1.0

Published by gateway.pipeworx.io — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Norway's official company/business register (BRREG) data exposed as MCP tools.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([ask_pipeworx, search_within, deep_research, polymarket_kalshi_spread]) co-exist with external-action tools ([subscribe]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [ask_pipeworx, search_within, deep_research, polymarket_kalshi_spread] → sinks [subscribe]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow ask_pipeworx → subscribe

Tools 37

Each tool and what it can reach — enumerated from the running server.

  • ask_pipeworxingests untrusted input
  • deep_researchingests untrusted input
  • polymarket_kalshi_spreadingests untrusted input
  • search_withiningests untrusted input
  • subscribenetwork egress
  • ai_visibility_checkno sensitive capability
  • ask_pipeworx_betano sensitive capability
  • ask_pipeworx_groundedno sensitive capability
  • bet_researchno sensitive capability
  • compare_entitiesno sensitive capability
Show 27 more tools ↓
  • discover_toolsno sensitive capability
  • entity_profileno sensitive capability
  • forgetno sensitive capability
  • generate_llms_txtno sensitive capability
  • get_accountsno sensitive capability
  • get_entityno sensitive capability
  • get_rolesno sensitive capability
  • get_sub_entityno sensitive capability
  • list_subscriptionsno sensitive capability
  • pipeworx_feedbackno sensitive capability
  • pipeworx_trendingno sensitive capability
  • polymarket_arbitrageno sensitive capability
  • polymarket_edge_trackerno sensitive capability
  • polymarket_edgesno sensitive capability
  • polymarket_fill_riskno sensitive capability
  • recallno sensitive capability
  • recent_alertsno sensitive capability
  • recent_changesno sensitive capability
  • rememberno sensitive capability
  • resolve_entityno sensitive capability
  • scan_competitor_ai_presenceno sensitive capability
  • scan_dependencyno sensitive capability
  • search_entitiesno sensitive capability
  • search_sub_entitiesno sensitive capability
  • suggest_questionsno sensitive capability
  • unsubscribeno sensitive capability
  • validate_claimno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.0 latest A 97/100 1 1.10.0 2026-07-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/gateway-pipeworx-io-brreg-no/badge.svg)](https://mcptrustchecker.com/registry/gateway-pipeworx-io-brreg-no)
HTML
<a href="https://mcptrustchecker.com/registry/gateway-pipeworx-io-brreg-no"><img src="https://mcptrustchecker.com/registry/gateway-pipeworx-io-brreg-no/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/gateway-pipeworx-io-brreg-no/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://gateway.pipeworx.io/brreg-no/mcp --online

Use the free API → How scoring works

More in Business & CRM