io.github.Mnymann/nordic-data MCP Server

The Model Context Protocol (MCP) server io.github.Mnymann/nordic-data provides AI agents access to company, KYB, VAT, sanctions, LEI, and address data for 15 EU countries. It exposes tools (11 total) for looking up companies, validating VAT numbers, running KYB reports, screening against sanctions lists, and address autocomplete.

🛠️ Key Features

Data coverage across 15 EU countries
Company data access
VAT number validation
KYB reports
Sanctions screening
LEI and address data lookup

🚀 Use Cases

Compliance workflows needing company and KYB data
VAT validation for B2B onboarding
Sanctions screening for business counterparties
Address autocomplete and address resolution

⚡ Developer Benefits

Built for Model Context Protocol (MCP) integrations
Tooling includes 11 MCP tools
Topics align with compliance and EU company data (e.g., kyb, kyc, lei, vat-validation, sanctions-screening)

⚠️ Limitations

Scope is described as official European business data across 15 EU countries

Nordic Data MCP Server

A Model Context Protocol server that gives AI agents (Claude, Cursor, Claude Code, ChatGPT, Copilot, etc.) direct access to official European business data across 15 European countries.

Look up companies, validate VAT numbers, run KYB reports, screen against sanctions lists, autocomplete addresses, and resolve LEI ownership — all from inside your AI assistant.

code

DK · NO · SE · FI · IE · UK · FR · DE · CZ · PL · LV · EE · NL · BE · LU

NL and DE require a Starter+ subscription (free-tier API keys receive HTTP 402 upgrade_required). On paid tiers, NL calls cost 5x quota units and DE calls cost 3x; all other countries cost 1x.

Quick start

1. Get an API key

2. Add to Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows):

json

{
  "mcpServers": {
    "nordic-data": {
      "command": "npx",
      "args": ["-y", "nordic-data-mcp"],
      "env": {
        "NORDIC_API_KEY": "YOUR_KEY_HERE"
      }
    }
  }
}

Restart Claude Desktop. You should see "nordic-data" appear in the tools menu.

3. Add to Cursor

In Cursor settings → MCP → Add new server, or edit ~/.cursor/mcp.json:

json

{
  "mcpServers": {
    "nordic-data": {
      "command": "npx",
      "args": ["-y", "nordic-data-mcp"],
      "env": {
        "NORDIC_API_KEY": "YOUR_KEY_HERE"
      }
    }
  }
}

4. Add to Claude Code

bash

claude mcp add nordic-data --env NORDIC_API_KEY=YOUR_KEY_HERE -- npx -y nordic-data-mcp

5. Add to ChatGPT (Pro, Business, or Enterprise)

ChatGPT supports remote MCP servers as custom connectors. No API key needed from you — the hosted server handles upstream authentication.

ChatGPT → Settings → Connectors → Add custom connector
URL: https://nordic-data-mcp-production.up.railway.app/mcp
Done — all 11 tools are available immediately.

Custom connectors require a ChatGPT Pro, Business, Team, or Enterprise plan.

6. Add to Claude.ai (web)

Same hosted endpoint, no local install:

Claude.ai → Settings → Connectors → Add custom connector
URL: https://nordic-data-mcp-production.up.railway.app/mcp
Done.

Available tools

Tool	What it does
`lookup_company`	Basic company data from official registries (CVR, Brønnøysund, Bolagsverket, Companies House, INSEE, etc.)
`validate_vat`	Validate a VAT number for the 27 EU member states against VIES
`screen_sanctions`	Bulk screen up to 1000 names against UN/EU/UK/OFAC/PEP lists (UK = FCDO UK Sanctions List; 745K+ entries)
`kyb_full`	Master Know-Your-Business report — identity, persons, financials, LEI, VAT, sanctions, adverse media, risk score
`autocomplete_address`	Address autocomplete with coordinates for DK (DAWA), NO (Kartverket), FR (BAN), SE and FI (OpenStreetMap Nominatim)
`lookup_lei`	GLEIF Legal Entity Identifier lookup — forward, reverse, and parent/children relationships
`company_enriched`	Company registry data + national industry statistics in one call (DK, NO, SE, FI)
`fr_history`	French company history timeline (name, activity, status, legal-form changes) from INSEE Sirene bitemporal data
`list_endpoints`	Discovery: list all read-only data endpoints in the underlying API (230+), with optional keyword filter
`get_endpoint_schema`	Discovery: full parameter + response schema for one endpoint, before calling it
`call_endpoint`	Discovery: execute a read-only request (GET/HEAD, plus three allowlisted POST screening queries) against any discovered endpoint

Example agent prompts

"Look up CVR 61056416 in Denmark" → calls lookup_company { country: "dk", id: "61056416" } → Carlsberg A/S

"Run a full KYB report on Equinor (NO 923609016)" → calls kyb_full { country: "no", id: "923609016" }

"Is LU26375245 a valid VAT number?" → calls validate_vat { country: "LU", vat_number: "26375245" }

"Screen these names against sanctions: Vladimir Putin, Acme Corp, John Smith" → calls screen_sanctions { names: [...] }

"Find the LEI for Tesco UK (00445790) and include parent and subsidiaries" → calls lookup_lei { mode: "reverse", country: "uk", id: "00445790" }

Country / ID format reference

Country	ID type	Format
DK	CVR	8 digits
NO	Organisasjonsnummer	9 digits
SE	Organisationsnummer	10 digits (with or without dash)
FI	Y-tunnus	`NNNNNNN-D` (7 digits + check digit)
IE	CRO number	1–7 digits
UK	Companies House	8 chars (digits, or prefix like `SC`, `NI`, `OC`)
FR	SIREN	9 digits
DE	LEI or HRB	LEI = 20 alphanum; HRB = prefix + digits
CZ	IČO	8 digits
PL	NIP / REGON / KRS	NIP=10, REGON=9/14, KRS=10
LV	Reģistrācijas nr.	11 digits
EE	Registrikood	8 digits
NL	KvK-nummer	8 digits
BE	BCE/KBO	10 digits
LU	RCSL	`B` + digits

The table above applies to lookup_company, kyb_full and lookup_lei (reverse mode). company_enriched covers DK, NO, SE and FI; autocomplete_address covers DK, NO, SE, FI and FR.

For validate_vat, country codes are uppercase VIES codes for the 27 EU member states — use EL (not GR) for Greece. The United Kingdom and Norway are not supported.

Configuration

The only environment variable you need to set is:

Variable	Required	Description
`NORDIC_API_KEY`	yes	Your API key from addonnordic.com

That's it. The MCP server connects to the hosted Nordic Data API for you.

Self-hosting (remote HTTP transport)

For remote MCP hosting (e.g. Anthropic Connectors, Smithery, web-based clients), deploy the bundled Streamable HTTP transport:

bash

npm install
npm run build
NORDIC_API_KEY=sk_... npm run start:http   # listens on :$PORT (default 3000)

Endpoints:

GET /healthz — health check (returns version + status)
ALL /mcp — public MCP endpoint. No key required; all upstream calls are billed to the server's own NORDIC_API_KEY (freemium / discovery). Per-IP rate-limited.
ALL /mcp/auth — authenticated MCP endpoint. Requires Authorization: Bearer ndk_... on every request; each call is billed to that customer's own key + quota.

Both are session-based via the Mcp-Session-Id header.

Connecting a remote client

This server uses static API-key authentication, not OAuth. How you connect depends on your client:

Header-capable clients (Claude Code, Cursor, Smithery, Claude.ai / ChatGPT custom connectors): point them at …/mcp/auth and supply your key as Authorization: Bearer ndk_.... Each request is billed to your own tenant + quota.
Generic / auto-discovery clients that only know "URL + OAuth": point them at the public …/mcp (no key). Otherwise such clients attempt OAuth Dynamic Client Registration (POST /register) and fail — this server has no OAuth endpoints by design and answers them with a clear JSON oauth_not_supported error (not a sign-in flow).
Local clients: prefer the stdio package — npx -y nordic-data-mcp with NORDIC_API_KEY set (see Quick start above).

Full OAuth 2.1 (so arbitrary external clients can self-onboard with their own key) is a planned Phase-2 item, not yet implemented.

A railway.toml is included for one-click deploy on Railway:

New Project → Deploy from GitHub repo → select Mnymann/nordic-data-mcp
Set Root Directory to nordic-data-mcp
Add env var NORDIC_API_KEY
Railway auto-detects the config, builds, and exposes a public HTTPS URL

Design notes

Thin adapter. No business logic, no caching, no transformations. Each tool maps 1:1 to a Nordic Data API endpoint.
No PII in logs. Request and response bodies are never logged.
API key required. The process refuses to start without NORDIC_API_KEY.
Rate limiting. The backend enforces per-key quotas; the HTTP transport additionally applies a per-IP limit on the public /mcp endpoint as defense-in-depth (tunable via PUBLIC_RATE_LIMIT / PUBLIC_RATE_WINDOW_MS). Caching is handled upstream.
Inputs are validated with zod before any HTTP call.

Contributing

Issues and PRs welcome at github.com/Mnymann/nordic-data-mcp.

Please do not include API keys, request bodies, or response payloads in bug reports.

Disclaimer

Nordic Data returns informational decision-support aggregated from official and public sources. It is not legal, compliance, financial, or professional advice, and not a definitive determination. KYB reports, sanctions/PEP matches, adverse-media hits, and risk scores are signals to review, not verdicts — verify independently and apply your own professional judgment before acting. Use of the service is subject to the AddonNordic Terms.

names	array	required	Array of person or company names to screen. Max 1000 names per call.
min_score	number	optional	Minimum fuzzy match score, 0-1. Default 0.7. Lower values return more (lower-confidence) matches.
fuzzy	boolean	optional	Enable fuzzy matching. Default true.

country	string	required	ISO 3166-1 alpha-2 country code, lowercase. Only dk, no, se, fi and fr are supported.
query	string	required	Partial address — street name, postcode, city, or any combination. Min 2 characters.

mode	string	required	'lei' = look up by LEI directly. 'reverse' = look up LEI from national company number.
lei	string	optional	20-character ISO 17442 Legal Entity Identifier. Required when mode='lei'.
country	string	optional	ISO 3166-1 alpha-2 country code, lowercase. Required when mode='reverse'.
id	string	optional	National company ID. Required when mode='reverse'.
include_relationships	boolean	optional	If true, also fetch parent and child entities. Only applies when mode='lei'.

path	string	required	Endpoint path from list_endpoints, e.g. '/api/company/{country}/{id}'. Concrete paths like '/api/company/dk/22756214' are also accepted.
method	string	optional	HTTP method for the endpoint (e.g. GET, POST). Defaults to GET. Must be a method the endpoint actually defines.

method	string	optional	HTTP method to use. Read-only methods only: GET or HEAD, plus POST solely for the allowlisted screening query endpoints (/api/sanctions/screen, /api/adverse/screen, /api/peps/nl/screen). Defaults to GET.
path	string	required	Concrete endpoint path, e.g. '/api/company/dk/22756214'. Path templates with {placeholders} are also accepted when you supply the values in `params`.
params	object	optional	Parameters for the call. Values whose keys match {placeholders} in the path are substituted into the path. Remaining values become query-string params for GET/DELETE, or the JSON request body for POST/PUT/PATCH.

io.github.Mnymann/nordic-data

io.github.Mnymann/nordic-data MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

lookup_company

validate_vat

screen_sanctions

kyb_full

autocomplete_address

lookup_lei

company_enriched

fr_history

list_endpoints

get_endpoint_schema

call_endpoint

Nordic Data MCP Server

Quick start

1. Get an API key

2. Add to Claude Desktop

3. Add to Cursor

4. Add to Claude Code

5. Add to ChatGPT (Pro, Business, or Enterprise)

6. Add to Claude.ai (web)

Available tools

Example agent prompts

Country / ID format reference

Configuration

Self-hosting (remote HTTP transport)

Connecting a remote client

Design notes

Contributing

Disclaimer

License

Install

Configuration

Related servers

country	string	required	ISO 3166-1 alpha-2 country code, lowercase. One of: dk, no, se, fi, ie, uk, fr, de, cz, pl, lv, ee, nl, be, lu.
id	string	required	National company identifier. DK=CVR (8 digits), NO=orgnr (9), SE=orgnr (10), FI=Y-tunnus (NNNNNNN-D), IE=CRO (1-7), UK=8 chars, FR=SIREN (9), DE=HRB number, CZ=IČO (8), PL=NIP (10) or KRS (10), LV=11 digits, EE=8 digits, NL=KvK (8 digits), BE=BCE/KBO (10 digits), LU=RCSL (B + digits).