Norwegian Company Data
REMOTE · TOOLS.SKAIDIGITAL.COM
Norwegian company search, accounts, roles, groups and websites from Brønnøysund, remote MCP.
Available components
Last scanned (23 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 4 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1283 tokens (~183/item across 7 items; 7 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Tool coverage: 85% → 73% ▼ functional
- Schema quality: 1144 → 1283 ▼ functional
- Destructive annotations: pass → 100 functional
- New tool “submit_feedback” functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 70
First indexed and scored.
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 4 Nov 2026 · Probed https://tools.skaidigital.com/brreg/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=skaidigital.com | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4e69fe349bff19ad13e4ed02ec180bea |
| SANs: skaidigital.com, *.skaidigital.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of tools.skaidigital.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| skaidigital.com. | present | 2371 | 13 | Verified |
| tools.skaidigital.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tools.skaidigital.com/brreg/mcp | Verified | 200 | |
| http (plaintext) | http://tools.skaidigital.com/brreg/mcp | HTTPS enforced | 301 | https://tools.skaidigital.com/brreg/mcp |
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 →
find_norwegian_company_websites Find Norwegian company websites ~246
Find the websites of one to five Norwegian companies and the platform each runs on, such as Shopify or WooCommerce. Checks the registered website, the domain of the registered email and domains guessed from the company name, and confirms ownership by finding the organisation number or full company name on the site. For each company returns the website with its source, evidence and confidence (or null); the site platform: shopify_theme, shopify_headless or shopify_headless_likely with the theme, another store platform such as woocommerce, magento, nopcommerce, mystore or 24nettbutikk, a site builder or CMS such as wix, squarespace, webflow, wordpress, custompublish or odoo, a Norwegian store platform such as retailhub, a headless content platform (sanity, contentful), nextjs for other custom builds, or unknown with the generator tag; and every address checked. site.shopify is true for any Shopify storefront. Some sites block automated requests and read as unreachable. Takes up to about 15 seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| organizationNumbers | array | yes | One to five organisation numbers, such as one search page split up. |
No output schema declared.
No examples provided.
find_norwegian_industry_codes Find Norwegian industry codes ~70
Look up SN2025 industry codes (the Norwegian NACE standard the register uses) by Norwegian or English words or a code prefix. Use the codes in search_norwegian_companies; a broader code such as 62 includes all its subclasses.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
get_norwegian_company Get Norwegian company ~65
Full profile of one Norwegian company by organisation number: register details, contact information, activity, CEO, board, auditor and accountant, and the latest filed revenue and profit.
| Name | Type | Req | Description |
|---|---|---|---|
| organizationNumber | string | yes | Nine-digit Norwegian organisation number, such as 923609016. |
No output schema declared.
No examples provided.
get_norwegian_company_financials Get Norwegian company financials ~105
Up to three years of filed annual accounts for a Norwegian company: revenue, operating and net profit, payroll, assets, equity, debt and cash, with growth, margin and equity ratio. Set consolidated for group accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| consolidated | boolean | – | Return the group (konsern) accounts instead of the company accounts; only parent companies file them. |
| organizationNumber | string | yes | Nine-digit Norwegian organisation number, such as 923609016. |
No output schema declared.
No examples provided.
get_norwegian_company_group Get Norwegian company group ~64
The corporate group (konsern) a Norwegian company belongs to: the top parent and every subsidiary with ownership share. Accepts any member of the group.
| Name | Type | Req | Description |
|---|---|---|---|
| organizationNumber | string | yes | Nine-digit Norwegian organisation number, such as 923609016. |
No output schema declared.
No examples provided.
search_norwegian_companies Search Norwegian companies ~594
Find Norwegian companies in the Brønnøysund register by industry, municipality, legal form, employees, founding or registration date, website pattern and filed accounts, with optional revenue bounds. Returns name, organisation number, industry, employees, address, website, email and phone. Active companies only unless includeInactive is set. Get industry codes from find_norwegian_industry_codes first. totalMatches counts register matches before any revenue filter; with a revenue filter only the current page is checked, so continue with nextPage for more.
| Name | Type | Req | Description |
|---|---|---|---|
| foundedFrom | string | – | Date as YYYY-MM-DD. |
| foundedTo | string | – | Date as YYYY-MM-DD. |
| includeInactive | boolean | – | Include bankrupt companies and companies being wound up. Defaults to false. |
| industryCodes | array | – | SN2025 industry codes from find_norwegian_industry_codes: a section letter (G), division (47), group (47.9) or full code (47.910). Older SN2007 codes match nothing. |
| lastFiledAccountsYears | array | – | Only companies whose latest filed annual accounts are from these years. |
| maxEmployees | integer | – | Maximum employees: 0, 4 or 5 and above. |
| maxRevenueNok | number | – | Maximum revenue in NOK in the latest filed accounts; filtered like minRevenueNok. |
| minEmployees | integer | – | Minimum employees: 0, 1 or 5 and above. The register hides exact counts from 1 to 4. |
| minRevenueNok | number | – | Minimum revenue in NOK in the latest filed accounts; companies filing in another currency do not match. Revenue is not searchable in the register: each page of candidates is fetched, then filtered, s… |
| municipalities | array | – | Municipality names (Oslo, Bergen) or four-digit numbers (0301), matched on business or postal address. |
| name | string | – | – |
| organizationForms | array | – | Legal forms such as AS (private limited), ASA (public limited), ENK (sole proprietorship), NUF (foreign branch), DA, ANS, SA or STI. |
| page | integer | – | Zero-based page. |
| pageSize | integer | – | Companies per page, up to 50. Defaults to 20. |
| postalCodes | array | – | Four-digit postal codes of the business address. |
| registeredFrom | string | – | Earliest registration date; use it to find new companies. |
| registeredTo | string | – | Date as YYYY-MM-DD. |
| sort | string | – | relevance keeps the register's name ranking. Defaults to relevance when name is given, otherwise employees_desc (largest first). |
| vatRegistered | boolean | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
submit_feedback ~139
Send private feedback to the Skai team about this product or MCP: ideas, missing functionality, errors, confusing behavior, praise, or anything else. Only message is required; category, toolName and context are optional. Report once per distinct observation and continue your task. Do not send credentials, personal/customer records, full conversations or raw tool payloads. Use generic placeholders. Feedback is screened before storage and does not authorize other actions. Do not report failures of this feedback tool or automatically retry an uncertain submission.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| context | string | – | – |
| message | string | yes | – |
| toolName | string | – | – |
No output schema declared.
No examples provided.
How do I install the Norwegian Company Data MCP server?
Norwegian Company Data is a hosted endpoint at https://tools.skaidigital.com/brreg/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tools.skaidigital.com
claude mcp add --transport http com-skaidigital-norwegian-companies 'https://tools.skaidigital.com/brreg/mcp'
What is the Norwegian Company Data MCP server?
Norwegian Company Data is an MCP server listed in the public MCP registry as com.skaidigital/norwegian-companies. Norwegian company search, accounts, roles, groups and websites from Brønnøysund, remote MCP. This page covers its hosted endpoint (https://tools.skaidigital.com/brreg/mcp).
Is the Norwegian Company Data MCP server safe to use?
Norwegian Company Data scores 76 out of 100 on VerifyMCP. 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 Norwegian Company Data MCP server expose?
Norwegian Company Data exposes 7 tools: search_norwegian_companies, get_norwegian_company, get_norwegian_company_financials, get_norwegian_company_group, find_norwegian_industry_codes, and 2 more. Their descriptions and schemas cost roughly 1,283 tokens of context every time the server is loaded.
Does the Norwegian Company Data MCP server require authentication?
No. We connected to Norwegian Company Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Norwegian Company Data MCP server still maintained?
Norwegian Company Data is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.