Nordic Data

io.github.Mnymann由 GitHub 账号 Mnymann 发布v1.5.6更新于 Oct 25, 2026

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

已验证Streamable HTTP可网页运行金融数据与分析商业与电商

概览

AI 生成的概览

Nordic Data 让助手查询欧洲官方企业数据:公司信息、增值税校验、KYB 报告、制裁筛查、LEI 与地址数据,覆盖 15 个国家。

可以做什么
查询 15 个欧洲国家的公司注册信息及含行业统计的增强公司记录,并提供法国公司变更时间线。对照 VIES 校验 27 个欧盟成员国的增值税号。将最多 1000 个人名或公司名与联合国、欧盟、英国及美国 OFAC 制裁名单和 PEP 名单进行筛查。生成完整 KYB 报告,汇总身份、人员、财务、LEI、增值税、制裁与风险信号。通过 GLEIF 解析 LEI,包括母公司与子公司关系,并提供带坐标的地址自动补全。借助基于 OpenAPI 的元工具发现并调用其他只读 API 端点。
适用场景
适合在入驻、开票、付款或签约前核实交易对手,或需要处理欧洲各司法辖区的公司、增值税、LEI 或地址数据时使用。
运行要求
需要来自 addonnordic.com 的 Nordic Data API 密钥:本地 npm 包通过 NORDIC_API_KEY 提供,认证远程端点通过 Authorization bearer 头提供。npx 包需要 Node.js,并需能访问托管 API。可选 NORDIC_DEFAULT_COUNTRY 与 NORDIC_VERBOSE_ERRORS。
安装前请注意
需要 API 密钥,每次查询按配额计费;免费额度有限,NL 与 DE 需付费套餐,且 NL 与 DE 调用消耗更多配额单位。公开远程端点无需密钥,但费用计入运营方自己的密钥,并按 IP 限流。返回结果是决策参考信号,而非法律或合规结论,应独立核实。服务会将查询发送给第三方注册机构与制裁数据源。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Nordic Data,将其添加到工作区。
  2. 连接 Authorization token 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.Mnymann%2Fnordic-data/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "nordic-data": {
      "type": "http",
      "url": "https://nordic-data-mcp-production.up.railway.app/mcp/auth",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Nordic Data MCP Server

[npm version] [License: MIT]

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.

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

Sign up at addonnordic.com and grab your NORDIC_API_KEY. Free tier available.

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.

  1. ChatGPT → Settings → Connectors → Add custom connector
  2. URL: https://nordic-data-mcp-production.up.railway.app/mcp
  3. 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:

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

Available tools

ToolWhat it does
lookup_companyBasic company data from official registries (CVR, Brønnøysund, Bolagsverket, Companies House, INSEE, etc.)
validate_vatValidate a VAT number for the 27 EU member states against VIES
screen_sanctionsBulk screen up to 1000 names against UN/EU/UK/OFAC/PEP lists (UK = FCDO UK Sanctions List; 745K+ entries)
kyb_fullMaster Know-Your-Business report — identity, persons, financials, LEI, VAT, sanctions, adverse media, risk score
autocomplete_addressAddress autocomplete with coordinates for DK (DAWA), NO (Kartverket), FR (BAN), SE and FI (OpenStreetMap Nominatim)
lookup_leiGLEIF Legal Entity Identifier lookup — forward, reverse, and parent/children relationships
company_enrichedCompany registry data + national industry statistics in one call (DK, NO, SE, FI)
fr_historyFrench company history timeline (name, activity, status, legal-form changes) from INSEE Sirene bitemporal data
list_endpointsDiscovery: list all read-only data endpoints in the underlying API (230+), with optional keyword filter
get_endpoint_schemaDiscovery: full parameter + response schema for one endpoint, before calling it
call_endpointDiscovery: 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

CountryID typeFormat
DKCVR8 digits
NOOrganisasjonsnummer9 digits
SEOrganisationsnummer10 digits (with or without dash)
FIY-tunnusNNNNNNN-D (7 digits + check digit)
IECRO number1–7 digits
UKCompanies House8 chars (digits, or prefix like SC, NI, OC)
FRSIREN9 digits
DELEI or HRBLEI = 20 alphanum; HRB = prefix + digits
CZIČO8 digits
PLNIP / REGON / KRSNIP=10, REGON=9/14, KRS=10
LVReģistrācijas nr.11 digits
EERegistrikood8 digits
NLKvK-nummer8 digits
BEBCE/KBO10 digits
LURCSLB + 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:

VariableRequiredDescription
NORDIC_API_KEYyesYour 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 installnpm run buildNORDIC_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:

  1. New Project → Deploy from GitHub repo → select Mnymann/nordic-data-mcp
  2. Set Root Directory to nordic-data-mcp
  3. Add env var NORDIC_API_KEY
  4. 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.


License

MIT © AddonNordic ApS

来源:README.md,提交 be2733a

工具

11

lookup_company

Look Up 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.

输入参数id必填country必填

validate_vat

Validate VAT Number

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.

输入参数country必填vat_number必填

screen_sanctions

Screen Sanctions and PEP Lists

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.

输入参数fuzzynames必填min_scorebirth_yearentity_type

kyb_full

Full KYB Report

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.

输入参数id必填country必填

autocomplete_address

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.

输入参数query必填country必填

lookup_lei

Look Up 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.

输入参数idleimode必填countryinclude_relationships

company_enriched

Enriched Company Profile

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).

输入参数id必填country必填

fr_history

French Company 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.

输入参数siren必填

list_endpoints

List API 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.

输入参数search

get_endpoint_schema

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.

输入参数path必填method

call_endpoint

Call API 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.

输入参数path必填methodparams

版本历史

1
  1. v1.5.6最新Sep 16, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。