API archive entry · source-reported
EU Nordic Open Data
EU tenders, sanctions, VIES VAT, ECB FX, ENISA EUVD, GLEIF LEI and Finnish/Norwegian registries
From the publisher
README & documentation
Source previewRead the project’s overview, installation instructions and usage examples. The original README is the source of truth.
13 production-ready Model Context Protocol (MCP) servers (@modelcontextprotocol/sdk over stdio) and 13 public hosted Apify Actors on the Apify Store (15 tools in total) built on official European Union, Finnish, Norwegian, French and UK government open-data APIs. The unified server (npx -y eu-nordic-open-data-mcp) exposes all 49 tools over stdio. Every tool shares a single core library (src/lib/) across its stdio MCP server (src/mcp-server.js) and Apify Actor (src/main.js), and enforces: Add any combination of the 13 hosted actors (all 13 shown below) to your claudedesktopconfig.json or .cursor/mcp.json: examples/ contains importable n8n workflows (daily EU tender alert by CPV…
Read the full README ↗ · Preview checked 2026-11-13T19:09:41.893Z
Inside the original README — Document outline
- EU & Nordic Official Open-Data MCP Servers & Apify Actors (eu-nordic-open-data-mcp)
- All 15 Tools at a Glance
- Quickstart 1: Zero-Install Hosted MCP in Claude Desktop & Cursor (@apify/actors-mcp-server)
- Examples: n8n workflows and LangChain / LangGraph
- Quickstart 2: Run Locally as Stdio MCP Servers
- Quickstart 3: n8n, Make.com & Sync REST API (run-sync-get-dataset-items)
- Licence & Attribution Register
Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.
Links from the README
References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.
Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.
Where these facts came from
AltAPIs imported it from public-apis/public-apis. The source link and dates remain visible for independent inspection.
What is reported
- Name, category, and short description
- Authentication label
- HTTPS and CORS labels
- Provider/source URL
What is not established
- Current uptime or availability
- Pricing, quotas, and rate limits
- Security, compliance, or licensing posture
- SDK quality or endpoint completeness
Record checkpoints
- First observed: Nov 13, 2026
- Last directory-field change: Nov 13, 2026
- Current source observation: Nov 13, 2026
Source reference
This page separates source-reported facts from questions that need live provider verification.