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.7nashinick/norwegian-data-mcp

PYPI · NORWEGIAN-DATA-MCP

Norwegian public data: companies, statistics, exchange rates, addresses, property. Zero API keys.

Available components

0 this week 94 Trust /100

Last scanned (3 hours ago)

Scores higher than 97% of PyPI servers

Category Data and Analytics

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to 7nashinick/norwegian-data-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 68 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2177 tokens (~155/item across 14 items; 14 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 68% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 2 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 1 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 31 Oct 26 +1
    • Stability: 0.97 → pass security
  • 30 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 23 Oct 26 −16
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +1
    • Stability: 0.97 → pass security
  • 15 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
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 5 Nov 2026 · Analysed pypi/norwegian-data-mcp@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo 7nashinick/norwegian-data-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/7nashinick/norwegian-data-mcp/.github/workflows/release.yml@refs/tags/v0.2.0
Rekor log index 2621486774
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:88a8ba6811221d51ab3c677d12eeabdfc5a6a340720e5bbe3eb210a621cb94f7

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 31 packages
Packages resolved 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~2,104 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 ~124

Full record for one Norwegian company by its 9-digit organisation number (orgnr): registered name, business and postal address, industry codes with text, organisational form, employee count, registration dates, VAT registration, bankruptcy/dissolution status, institutional sector. Falls back to sub-unit (underenhet) lookup if the orgnr is a business location rather than a legal entity. Use search_companies first if you only have a name. Example: orgnr='923609016' (Equinor ASA).

NameTypeReqDescription
orgnrstringyes9-digit organisation number

Structured output declared, but exposes no named fields.

No examples provided.

get_company_financials ~159

Latest filed annual accounts (aarsregnskap) for a Norwegian company from Regnskapsregisteret: revenue (driftsinntekter), operating profit (driftsresultat), net result (aarsresultat), total assets (sumEiendeler), equity (egenkapital), debt split, accounting period and currency. Only the most recent filed year is available; a link to the official annual-report PDF is included. Answers 'what was X's revenue/profit'. Not available for all entities (sole proprietorships may not file); a clear 'no accounts filed' answer is returned, not an error. Example: orgnr='923609016'.

NameTypeReqDescription
orgnrstringyes9-digit organisation number

Structured output declared, but exposes no named fields.

No examples provided.

get_company_roles ~125

Board and management of a Norwegian company by orgnr: chair (styrets leder), board members, CEO (daglig leder), auditor (revisor), with names and resignation flags. Answers 'who is on the board of X', 'who runs X', 'who audits X'. Data from Enhetsregisteret; role holders can be persons or companies. Example: orgnr='923609016'.

NameTypeReqDescription
include_birth_datesboolean–Include role holders' birth dates (public data, omitted by default)
orgnrstringyes9-digit organisation number

Structured output declared, but exposes no named fields.

No examples provided.

get_exchange_rates ~136

Daily NOK exchange rates from Norges Bank (the central bank). Pass ISO currency codes; every column is normalized to NOK per 1 unit of the currency, most recent `periods` business days. Use for 'USD/NOK rate', 'how has the krone moved against the euro'. For interest rates use get_key_series(series='interest_rates') instead. Example: currencies=['USD', 'EUR'], periods=30.

NameTypeReqDescription
currenciesarrayyesISO 4217 codes, e.g. ['USD', 'EUR', 'SEK', 'GBP']
periodsinteger–Number of most recent business days

Structured output declared, but exposes no named fields.

No examples provided.

get_group_structure ~111

Registered group structure (konsern) for a Norwegian company by orgnr: the parent and its subsidiaries as a nested tree with ownership stakes (eierandel). Answers 'what companies does X own', 'is X part of a group', 'who are X's subsidiaries'. Companies outside a registered group get a clear answer, not an error. Example: orgnr='923609016' (Equinor) returns its subsidiary tree.

NameTypeReqDescription
orgnrstringyes9-digit organisation number

Structured output declared, but exposes no named fields.

No examples provided.

get_key_series ~144

One-call shortcut for Norway's most-requested numbers, no table IDs needed: cpi (consumer price index + 12-month inflation), population, unemployment (LFS, seasonally adjusted), house_prices (existing-dwellings index), wages (average monthly earnings), interest_rates (NIBOR + Norges Bank policy rate). Returns the last `periods` observations. Use for 'what is inflation in Norway', 'Norway's population', 'Norwegian interest rates' instead of the search/info/fetch chain. Example: series='cpi', periods=24.

NameTypeReqDescription
periodsinteger–Number of most recent observations
seriesstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_place ~105

Search official Norwegian place names (stedsnavn): mountains, lakes, valleys, farms, islands, neighborhoods. Returns name, type (navneobjekttype), municipality, and coordinates. Use when the target is not a street address; for street addresses use search_address. Example: query='Galdhøpiggen'. Example: query='Preikestolen'.

NameTypeReqDescription
limitinteger––
querystringyesPlace name, wildcard * allowed

Structured output declared, but exposes no named fields.

No examples provided.

get_property ~193

Locate a Norwegian cadastral property (matrikkelenhet) by matrikkel number: kommunenummer + gardsnummer/bruksnummer (gnr/bnr), e.g. from a search_address result. Returns the property's representation point (lat/lon) and optionally its boundary polygon (GeoJSON). NOTE: Norway's open APIs do not expose owners, buildings, or valuations; those require a licensed Matrikkel agreement, so say so rather than guessing. Example: kommunenummer='0301', gardsnummer=207, bruksnummer=100.

NameTypeReqDescription
bruksnummerintegeryesHolding number (bnr)
festenummer––Leasehold number (fnr), if any
gardsnummerintegeryesFarm number (gnr)
include_boundaryboolean–Include GeoJSON boundary polygon (larger response)
kommunenummerstringyes4-digit municipality code

Structured output declared, but exposes no named fields.

No examples provided.

get_statistics ~211

Fetch numbers from an SSB table as a compact CSV table. With no selection, sensible defaults apply: totals where the table allows it and the last 12 periods, good for 'recent trend' questions. For breakdowns, pass selection mapping variable codes (from get_table_info) to value-code lists; expressions allowed: ['from(2020M01)'], ['top(24)'], ['*'] (all). If the table is closed, its successor is used or suggested in hints. Example: table_id='14700' (CPI) with no selection returns the last 12 months. Example: table_id='07459', selection={'Region': ['0301'], 'Tid': ['top(5)']} returns Oslo population for the last 5 years.

NameTypeReqDescription
langstring––
selection––variableCode -> value codes or expressions from(...) / top(n) / *
table_idstringyesSSB table ID, e.g. '14700'

Structured output declared, but exposes no named fields.

No examples provided.

get_table_info ~124

Structure of one SSB table before fetching data: its variables (dimensions), the value codes each accepts, time span, and any successor table if this one is closed. Use between search_statistics and get_statistics when you need a specific breakdown (region, industry, age group); skip it when defaults are fine (totals, recent periods). Example: table_id='07459' shows Region, Kjonn (sex), Alder (age), Tid (time) and their codes.

NameTypeReqDescription
table_idstringyesSSB table ID, e.g. '07459'

Structured output declared, but exposes no named fields.

No examples provided.

reverse_geocode ~103

Nearest official Norwegian addresses to a coordinate. Returns addresses with distance in meters, municipality, and cadastral identifiers. Use for 'what address is at lat X, lon Y' or to anchor GPS positions. Example: lat=59.9139, lon=10.7522, radius=100.

NameTypeReqDescription
latnumberyes–
limitinteger––
lonnumberyes–
radiusinteger–Search radius in meters

Structured output declared, but exposes no named fields.

No examples provided.

search_address ~159

Search official Norwegian addresses. Returns matched addresses with coordinates (lat/lon, EPSG:4258), municipality (kommune), postal code/place, and cadastral identifiers (gardsnummer/bruksnummer, i.e. gnr/bnr), so this also resolves address to property ID in one call. Handles partial input and typos. Use for 'where is <address>' and as the first step before get_property. For place names that are not street addresses (mountains, lakes, farms), use get_place. Example: query='Karl Johans gate 22, Oslo'.

NameTypeReqDescription
kommunenummer––Optional 4-digit municipality filter
limitinteger––
querystringyesFree-text address, partial OK

Structured output declared, but exposes no named fields.

No examples provided.

search_companies ~273

Search the Norwegian company register (Enhetsregisteret) by name and/or filters. Returns up to `limit` companies with orgnr (9-digit organisation number), organisational form, address, industry code (naeringskode, NACE), employee count, and status flags (konkurs = bankrupt, underAvvikling = being dissolved). Use when the user names a company without an orgnr or asks 'find companies that...'. If you already have an orgnr, call get_company instead. Example: name='Equinor'. Example: naeringskode='11.05' (breweries), kommunenummer='0301' (Oslo), min_employees=10.

NameTypeReqDescription
kommunenummer––4-digit municipality code, e.g. '0301' = Oslo
konkurs––true = only bankrupt companies
limitinteger––
max_employees–––
min_employees–––
naeringskode––NACE industry code, e.g. '11.05' or prefix '62'
name––Company name, full or partial
organisasjonsform––e.g. 'AS' (Ltd), 'ASA' (Plc), 'ENK' (sole prop.)
pageinteger––

Structured output declared, but exposes no named fields.

No examples provided.

search_statistics ~137

Search Statistics Norway's ~7,000 statistical tables by keyword. Returns table IDs with titles, time coverage, and last-updated dates. Always the first step for statistics questions unless get_key_series covers it (CPI, population, unemployment, house prices, wages, interest rates; use that instead, it is one call). After finding a table, call get_table_info to see its variables, then get_statistics to fetch numbers. Example: query='electricity prices household'. Example: query='innvandring' (Norwegian works too).

NameTypeReqDescription
limitinteger––
querystringyesKeywords, English or Norwegian

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.7nashinick/norwegian-data-mcp server?

io.github.7nashinick/norwegian-data-mcp runs locally as a PyPI package, launched with uvx norwegian-data-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · norwegian-data-mcp

# add to Claude Code
claude mcp add 7nashinick-norwegian-data-mcp -- uvx norwegian-data-mcp
Common questions

What is the io.github.7nashinick/norwegian-data-mcp server?

io.github.7nashinick/norwegian-data-mcp is listed in the public MCP registry as io.github.7nashinick/norwegian-data-mcp. Norwegian public data: companies, statistics, exchange rates, addresses, property. Zero API keys. This page covers its PyPI package (norwegian-data-mcp).

Is the io.github.7nashinick/norwegian-data-mcp server safe to use?

io.github.7nashinick/norwegian-data-mcp scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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.7nashinick/norwegian-data-mcp server expose?

io.github.7nashinick/norwegian-data-mcp exposes 14 tools: search_companies, get_company, get_company_roles, get_company_financials, get_group_structure, and 9 more. Their descriptions and schemas cost roughly 2,104 tokens of context every time the server is loaded.

Is the io.github.7nashinick/norwegian-data-mcp server still maintained?

io.github.7nashinick/norwegian-data-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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.7nashinick/norwegian-data-mcp server under?

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