Eurostat Labor Stats MCP Server
Pricing
from $50.00 / 1,000 tool calls
Eurostat Labor Stats MCP Server
An MCP server over the official Eurostat dissemination API (ec.europa.eu/eurostat) — EU workforce statistics for site-selection questions: unemployment, employment, activity, minimum wages and labour cost.
Pricing
from $50.00 / 1,000 tool calls
Rating
0.0
(0)
Developer
NexGen Watch
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 days ago
Last modified
Categories
Share
🧰 Eurostat Labor Stats MCP Server
An MCP server over the official Eurostat dissemination API (ec.europa.eu/eurostat) — EU
workforce statistics for site-selection questions: unemployment, employment, activity,
minimum wages and labour cost. Runs as an Apify Standby MCP server; connect an MCP client
at path /mcp.
This is a standby MCP server: it stays warm on Apify and answers tool calls from any MCP client (Claude Desktop, Cursor, an agent framework) at https://nexgenwatch--eurostat-labor-stats-mcp.apify.actor/mcp. Billing is pay-per-event: $0.05 when the server starts, then $0.05 per tool call (mcp-tool-call). Source: ec.europa.eu.
No login, no source API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.
📊 Sample Output
A standby server answers tool calls rather than writing a dataset, so the sample is the server's own live health answer (GET https://nexgenwatch--eurostat-labor-stats-mcp.apify.actor/, HTTP 200, read on 2026-09-17) followed by its tool table:
{"server": "eurostat-labor-stats","billing_gate": true,"declared_events": ["apify-actor-start","mcp-tool-call"],"scope": "The official Eurostat dissemination API: EU workforce statistics — unemployment, employment, activity, minimum wages and labour cost — answered for a bounded slice (dataset + country + period).","rate_limit_per_sec": 5.0,"rate_waits": 0,"ready": true}
| Tool | Arguments | What it returns |
|---|---|---|
list_labor_datasets | `` | List curated common EU labour-statistics datasets (Eurostat code + description). The get tool also accepts any other valid Eurostat dataset code. |
get_labor_figure | dataset: str, geo: str, period: str, filters: dict = None | Get the Eurostat figure(s) for a BOUNDED slice: one dataset, one country (geo), one period, optionally narrowed by extra dimensions (e.g. {'sex':'T','age':'Y15-74'}). An unknown dataset or an empty slice is a sourced-emp |
explain_limits | `` | What this server can and cannot tell you about Eurostat labour statistics. |
✅ What you get
3 tools, each returning a JSON object built only from what the source answered, with a scope and note field stating what the source does and does not cover. A lookup the source answers with 'not found' is a sourced answer (charged); malformed input or a source failure returns a notice that is NOT charged; nothing is ever fabricated.
Tools
get_labor_figure(dataset, geo, period, filters?)— the figure(s) for a bounded slice: one dataset, one country, one period (optionally narrowed by sex/age/unit).list_labor_datasets()— curated common labour datasets and their Eurostat codes.explain_limits()— scope, codes, and the bounded-only rule.
Billing
| Event | Price |
|---|---|
Server start (apify-actor-start) | $0.05, charged once per run by the platform |
Tool call (mcp-tool-call) | $0.05 per completed tool call |
One flat charge per completed tool call. A bounded query that returns figures and a sourced-empty result (unknown dataset via a 404, or an empty slice) are both answers and are charged. A malformed query (missing dataset/geo/period) or an upstream failure is a notice and is not charged. An unbounded query is refused (free) — the server never dumps a bulk table as one billed call; narrow it with more dimensions or a single period.
Source
The official Eurostat dissemination API (JSON-stat), queried anonymously (no key). geo uses
Eurostat country codes (DE, FR, EU27_2020); period is a year (2023) or month (2024-06).
⚙️ Sample inputs
1. Connect an MCP client (Claude Desktop / Cursor style config; your Apify API token goes in the header):
{"mcpServers": {"eurostat-labor-stats-mcp": {"url": "https://nexgenwatch--eurostat-labor-stats-mcp.apify.actor/mcp","headers": {"Authorization": "Bearer <YOUR_APIFY_TOKEN>"}}}}
2. One tool call over JSON-RPC (what the client sends to /mcp; each call is one mcp-tool-call event):
{"jsonrpc": "2.0","id": 1,"method": "tools/call","params": {"name": "list_labor_datasets","arguments": {}}}
3. Health check from a shell (free — no tool call is charged):
$curl -H "Authorization: Bearer $APIFY_TOKEN" https://nexgenwatch--eurostat-labor-stats-mcp.apify.actor/
🧾 JSON sample record
The live health record above is the server's own answer; a tool result carries the fields listed in the tool table plus scope and note.
🔧 How it works
Source. ec.europa.eu — endpoints: https://ec.europa.eu/eurostat/api/dissemination/statistics/1.0/data. Public, logged-out reads only.
Standby. Apify keeps one server process warm; each MCP session is served by that process and idle servers are stopped by the platform. Nothing is cached between calls except what the source itself caches.
Charging. Every tool call charges one mcp-tool-call at $0.05 through Apify's pay-per-event billing before the answer is returned; the declared events are asserted against the live pricing at startup (billing_gate in the health answer).
What is not done. No login, no CAPTCHA bypass, no private data, no scraping of pages the source does not publish to any visitor.
💰 Pricing example
| Event | Free | Bronze | Silver | Gold |
|---|---|---|---|---|
Actor Start (apify-actor-start) | $0.05 | $0.05 | $0.05 | $0.05 |
Tool call (mcp-tool-call) | $0.05 | $0.05 | $0.05 | $0.05 |
- 10 tool calls in one session: $0.05 start + 10 × $0.05 = $0.55
- 100 tool calls in one session: $0.05 start + 100 × $0.05 = $5.05
- 1000 tool calls in one session: $0.05 start + 1000 × $0.05 = $50.05
A health check or a connection that makes no tool call charges only the $0.05 start fee. A sourced 'not found' answer is a completed tool call and is charged; a notice for malformed input or a source failure is not charged (settle() charges only chargeable outcomes).
⚖️ Legal & ToS
The server reads public data published by ec.europa.eu to any visitor, identifies itself with a contact User-Agent, and does not access accounts or private data. Use the answers in line with the source's terms and your local law; the intended use is B2B research and agent tooling.
❓ FAQ
Q: Do I need a source API key?
A: No. ec.europa.eu is read logged-out. You need only your Apify API token to connect to the server.
Q: Which MCP clients work?
A: Any client that speaks the MCP HTTP transport: Claude Desktop, Cursor, Windsurf, LangChain/LlamaIndex MCP adapters and Apify's own MCP client. Point it at the /mcp URL above.
Q: What happens when the source has no answer?
A: A sourced 'not found' (for example a 404 for an unknown identifier) comes back as an answer with scope and note explaining what was checked (where the server carries those fields), and is charged as a completed call; malformed input or a source outage returns a notice that is not charged. Nothing is invented.
Q: How is a call billed?
A: One mcp-tool-call event per tool call at $0.05, plus $0.05 when the server starts. Idle time is not billed to you.
Q: Is it rate limited?
A: The server paces requests to the source and answers calls in the order they arrive.
Q: Can I call it without an MCP client?
A: Yes — the /mcp endpoint is plain JSON-RPC over HTTP (sample input 2), and GET / is a free health check.
🆘 Troubleshooting
- 401 / 403 from the server → the Authorization header is missing or the token is wrong → use
Bearer <your Apify API token>. - 400
Missing session ID→ the client hit/mcpwithout initialising an MCP session → let the MCP client connect (it performs the handshake); raw JSON-RPC needs the session header the initialise call returns. - Tool returns a notice instead of data → the input was malformed or empty, or the source failed → the call was not charged; check the
note/reasonfield, fix the input and call again. - First call is slow → the standby server was cold and Apify started it → later calls in the same session are fast.
🔗 Related Actors
- Cross-Border Sanctions Resolution MCP Server — Resolve a party name against the US OFAC SDN, EU consolidated and UK OFSI sanctions lists in one MCP call, with the match basis and each list's as-of…
- Crossref Citation MCP Server — An MCP server over the official Crossref REST API (api.crossref.org) — scholarly work
- EPO Publication Evidence MCP Server — Retrieve official European patent publications by number or publication day from the EPO publication server, with the INID-coded front page parsed in…
- FDIC Bank Diligence MCP Server — Answer questions about US banks from the FDIC's public data: institution details, structural history, current status, closures and failures - for vet…
- Federal Award Counterparty MCP Server — Answer questions about US federal award recipients from USAspending.gov: who won awards from an agency, one organisation's award history, and who tha…
- Federal Rule Impact MCP Server — Answer 'what regulations changed for this industry' from the US Federal Register: search and retrieve rules, proposed rules and notices by CFR title,…
- 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.
⭐ Found this useful?
If this server answered a question your agent could not, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.
