mcpbeat Sign in

Nordic Data MCP Server

answering

Nordic Data is answering right now. Last checked 10 min ago. 161 installs a week from npm. It exposes 11 tools. Last commit 28 Sep 2026.

Company, KYB, VAT, sanctions, LEI and address data for 15 EU countries.

Installs per day peak 63 · avg 15 · -37% w/w
a month agotoday
Uptime history 90 days of history · worst day 99%
90 days agonow
100.0%
Uptime 24h
91 of 91 checks
11
Tools
read from the server
206 ms
Response time
average over 24h
161
Installs / week
npm and PyPI

What changed 11

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 September 2026. No other catalogue keeps this.

28 Sep a tool description was rewritten screen_sanctions
28 Sep a tool changed version
27 Sep a tool changed the parameters it asks for screen_sanctions
27 Sep a tool changed version
15 Sep 3 tool descriptions were rewritten autocomplete_address, company_enriched, validate_vat
15 Sep 3 tools changed the parameters they ask for autocomplete_address, company_enriched, validate_vat
15 Sep a tool changed version

Nothing serious here today

Today is the operative word: we check Nordic Data every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add nordic-data --transport http https://nordic-data-mcp-production.up.railway.app/mcp/auth
Settings → Connectors → Add custom connector, then paste this address
https://nordic-data-mcp-production.up.railway.app/mcp/auth
~/.codex/config.toml
[mcp_servers.nordic-data]
url = "https://nordic-data-mcp-production.up.railway.app/mcp/auth"
.cursor/mcp.json
{
  "mcpServers": {
    "nordic-data": {
      "url": "https://nordic-data-mcp-production.up.railway.app/mcp/auth"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "nordic-data": {
      "type": "http",
      "url": "https://nordic-data-mcp-production.up.railway.app/mcp/auth"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

lookup
lookup_company
Call before onboarding a supplier or customer to confirm the legal entity exists and is active. Look up basic company data (name, address, status, industry, VAT registration, founding date) from official European business registries. Supports 15 countries: DK (CVR), NO (Brønnøysund), SE (Bolagsverket), FI (YTJ/PRH), IE (CRO), UK (Companies House), FR (INSEE Sirene), DE (Handelsregister), CZ (ARES), PL (KAS+KRS), LV (Uzņēmumu reģistrs), EE (Ariregister), NL (KvK), BE (KBO), LU (RCSL). Tier note: NL and DE use paid upstream registries (KvK and Handelsregister). Free-tier API keys will receive HTTP 402 with error 'upgrade_required' — do NOT retry on 402; the error message includes an upgrade URL. On paid tiers, NL calls cost 5x quota units and DE calls cost 3x; all other countries cost 1x.
lookup_lei
Look up a Legal Entity Identifier (LEI) via GLEIF — the global standard for entity identification. Returns legal name, registered address, status, parent + ultimate parent relationships, and child entities (subsidiaries). Also supports reverse lookup from a national company number to LEI across 15 countries (DK, NO, SE, FI, IE, UK, FR, DE, CZ, PL, LV, EE, NL, BE, LU). Tier note (reverse mode only): NL and DE use paid upstream registries — free-tier API keys receive HTTP 402 'upgrade_required'; do NOT retry on 402.
autocomplete
autocomplete_address
Address autocomplete with coordinates. Sources: DAWA (DK, official address register), Kartverket/Geonorge (NO, official), BAN (FR, official Base Adresse Nationale), and OpenStreetMap Nominatim (SE, FI). Returns ranked address suggestions with lat/lng and a match confidence. Supports 5 countries: DK, NO, SE, FI, FR.
call
call_endpoint
Discovery meta-tool. Executes a read-only HTTP request against the Nordic Data API for any data endpoint discovered via list_endpoints, and returns the response. Authenticates with the same scoped API key as the curated tools. Strictly read-only: only GET/HEAD requests are permitted, plus POST to three allowlisted screening endpoints (/api/sanctions/screen, /api/adverse/screen, /api/peps/nl/screen) that are pure queries using POST only to carry a large request body. All state-changing operations (watch lists, webhooks, DELETE/PUT/PATCH) and all /admin endpoints are refused. Use list_endpoints and get_endpoint_schema first to find the correct path, method, and parameters.
company
company_enriched
Company registry data plus national industry statistics in one call. Returns `company` (same shape as lookup_company) and `industryStats` — a time series from the national statistics office for the company's industry code (currently Danmarks Statistik for DK); `industryStats.available` is false when no statistics exist. Supports 4 countries: DK, NO, SE, FI. For other countries use lookup_company (basic registry data) or kyb_full (full due-diligence report).
endpoint
get_endpoint_schema
Discovery meta-tool. Returns the full parameter and response schema for a single Nordic Data API endpoint (path + method), read from the backend's live OpenAPI spec with $refs resolved inline. Use after list_endpoints to learn exactly which parameters an endpoint takes before calling it with call_endpoint. Admin endpoints are rejected.
endpoints
list_endpoints
Discovery meta-tool. Lists ALL available Nordic Data API data endpoints (HTTP method, path, short description) by reading the backend's live OpenAPI spec at runtime — far beyond the curated high-level tools. Use this to discover capabilities the dedicated tools do not cover, then call get_endpoint_schema for parameter details and call_endpoint to execute one. Only read-only operations are listed (GET/HEAD plus the POST screening queries); admin and state-changing endpoints are never returned. Supports an optional `search` keyword filter. The catalog has 230+ endpoints.
history
fr_history
French company history timeline. Returns one event per change to the company's name, activity (NAF code), status (active/closed), legal form, or social-economy flag, derived from INSEE Sirene 3.11's bitemporal periodesUniteLegale array. Includes 'initial:<field>' events that show the state at company creation (date, name, NAF code, etc.). Input: 9-digit SIREN number. Cost: 1 quota unit; free tier supported (France is not tier-gated, unlike NL and DE). Cache: 24h server-side. Errors: 400 invalid_id_format (not 9 digits), 403 non_diffusible (SIREN exists but is privacy-protected under art. R123-232-1), 404 not_found, 503 upstream_unavailable.
kyb
kyb_full
Run before a consequential decision — onboarding a counterparty, approving a payment, extending credit, or signing a contract. Full Know-Your-Business master report for a company across 15 EU countries (DK, NO, SE, FI, IE, UK, FR, DE, CZ, PL, LV, EE, NL, BE, LU). Aggregates 9 sections: identity, registered address (geocoded), key persons & directors, financial statements, official filings, LEI + corporate ownership, VAT registration, sanctions + PEP screening, adverse media (GDELT 2.0), and a composite risk score. Single call. Cold cache typically completes in 10-15s; warm cache returns in <100ms. Cached 6h on success, 60s when partial. Partial responses: if any of the 9 sections time out, the report still returns with 'truncated: true' and 'sectionsUnavailable: [{section, reason}]' — caller can retry in 60s for a complete report. Tier note: NL and DE use paid upstream registries — free-tier API keys receive HTTP 402 'upgrade_required'; do NOT retry on 402. On paid tiers, NL costs 5x quota and DE costs 3x. Disclaimer: this report is informational decision-support aggregated from official and public sources — NOT legal, compliance, or financial advice and not a definitive determination. The risk score and findings indicate areas to verify, not verdicts; the response includes a 'disclaimer' field stating this.
screen
screen_sanctions
Screen one or more person or company names against the UN, EU, UK (FCDO UK Sanctions List) and US OFAC sanctions lists plus PEPs (745K+ entries, UN direct and the rest via OpenSanctions). Typical use: counterparty checks before onboarding or processing a payment. Returns per-name match lists with fuzzy match scores, source-list attribution and risk topics, 'sourcesUsed' (each list actually screened, with its publisher's last-updated date), plus a 'disclaimer' field. Matches are informational decision-support from public sources, not legal or compliance advice — a match indicates a potential hit that requires verification, not a confirmed listing.
validate
validate_vat
Call before issuing an invoice, processing a cross-border payment, or storing a counterparty's VAT number. Validate a VAT registration number for any of the 27 EU member states against the official EU VIES service (DK is checked against the national CVR register). Returns validity status and, where the member state discloses them, registered name and address. Use EL for Greece. Not supported: United Kingdom (GB) and Norway (NO) — for a Norwegian company, lookup_company with country 'no' reports `vatRegistered` from Brønnøysund. HTTP 503 upstream_unavailable means that member state's VIES node is temporarily down; retry later.

Endpoints

URLTransportStateLatencyChecked
https://nordic-data-mcp-production.up.railway.app/mcp/auth streamable-http answering 190 ms 10 min ago

Alternatives to Nordic Data

same job, measured the same way
EU Business Data (VAT, EORI, company, sanctions, KYB)
by zifengw

EU VAT (VIES) and EORI validation, company registry, sanctions screening, KYB. Free tier, x402.

14 tools answering
Prometiam Company Data
by matiasmaquieira96

Company data and KYB API for 31 countries: monitoring, financial statements, insolvency, sanctions

1 742 installs/wk local only
Verify a Company
by hatchloop

Verify a company on GLEIF LEI and SEC EDGAR, screen sanctions. No key; quota-free data.

7 tools answering
Jsonpage
by jsonpage

Company data for 14 countries: search firms, check company IDs, validate VAT and EORI numbers.

answering
Clearparty
by clearparty

KYB for AI agents: GLEIF entity, parent chain, sanctions and EU VAT checks. Data lookup only.

answering
Ja Normalize
by kojimahyui01

Holidays/business days for 200+ countries; Japanese address, name, bank and company normalization.

46 installs/wk local only
Factline
by snefhew

EU company, sanctions, PEP and VAT checks, x402 pay guard, Dutch data. 5 checks a day free, no key.

64 tools answering
VATKit
by olsols4

Live EU VAT number checks via VIES with company name/address, VAT formats and EU VAT rates

answering

Nordic Data — questions

Answers built from our own checks of this server.

What can Nordic Data do?
It exposes 11 tools, read directly from the server on our last check. Among them: autocomplete_address, call_endpoint, company_enriched, fr_history, get_endpoint_schema, kyb_full and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Nordic Data working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 206 ms. The bar chart above shows every period we have measured.
How do I connect Nordic Data?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Nordic Data need an API key?
No. Nordic Data completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Nordic Data?
It answers our handshake in 206 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Nordic Data?
The npm package nordic-data-mcp was installed 161 times in the last week. Week over week that is -37%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Nordic Data open source?
The code is open source: it is published under the MIT licence, written in TypeScript and 1 stars on GitHub. The licence covers the code in the repository, not the hosted service at nordic-data-mcp-production.up.railway.app, which runs on its operator's own terms.