Command Palette

Search for a command to run...

UnylyUnyly
Browse all

ILO Statistics (ILOSTAT) Server

FreeNot checked

MCP server for accessing ILOSTAT (ILO statistical database) with tools to search indicators, retrieve metadata, list dimension values, and fetch data, with full

GitHubEmbed

About

MCP server for accessing ILOSTAT (ILO statistical database) with tools to search indicators, retrieve metadata, list dimension values, and fetch data, with full provenance tracking.

README

MCP CI Version Tools Resources Prompts npm MCP Registry ilo-mcp-server MCP server smithery badge License: MIT Status

🇧🇷 Leia em Português

A public, hosted, provenance-first MCP server for the International Labour Organization (ILO) statistics — the ILOSTAT database — no installation, no account, no API key. Point your MCP client at the hosted endpoint and ask about unemployment, employment, wages, working time and other labour indicators by country, year, sex and age. It runs on Cloudflare Workers over Streamable HTTP and talks to the official ILOSTAT SDMX REST API.

Independent project. This is an unofficial, community-built client of the ILO's public ILOSTAT API — not affiliated with or endorsed by the International Labour Organization. Data remain © ILO under CC BY 4.0; see Data license and attribution.

Every response carries a provenance block (source URL, data vintage, real retrieval timestamp, license, ILO citation) — exact figures with an audit trail, not numbers guessed from training data.

Use it (hosted — no setup)

Point any MCP client at the Streamable HTTP endpoint:

https://ilo.sidneybissoli.com/mcp

Claude Desktop / Claude Code and other clients with native remote support:

{
  "mcpServers": {
    "ilostat": {
      "url": "https://ilo.sidneybissoli.com/mcp"
    }
  }
}

For clients that launch MCP servers as a command, use the mcp-remote bridge:

{
  "mcpServers": {
    "ilostat": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://ilo.sidneybissoli.com/mcp"]
    }
  }
}

The ilo-mcp-server.sidneybissoli.workers.dev hostname is also served, as a secondary.

Run locally (stdio)

Prefer not to route queries through a third-party host? The same server also runs as a local stdio process that talks directly to the official ILOSTAT API — same 4 tools, resources and prompts, same limits, same provenance block, no Cloudflare in the loop.

No install needed — the package is on npm (ilo-mcp-server, Node ≥ 20):

{
  "mcpServers": {
    "ilostat": {
      "command": "npx",
      "args": ["-y", "ilo-mcp-server"]
    }
  }
}

Or from source:

git clone https://github.com/SidneyBissoli/ilo-mcp-server
cd ilo-mcp-server
npm install
npm run build
node dist/cli.js   # serves MCP over stdio (Ctrl+C to stop)

(then point the client at node /path/to/ilo-mcp-server/dist/cli.js).

Differences from the hosted server, all due to the absence of Cloudflare bindings: the SDMX cache lives in process memory (structures and codelists are reused within a session, not across sessions); the search catalogue is downloaded from the official endpoint on the first search (its real retrieved_at is reported in provenance); no usage metrics, rate limit or auth. Logs go to stderr — stdout carries only the JSON-RPC stream. The repository Dockerfile builds this runtime (used by the Glama registry).

Tools

Tool What it does Source
ilo_search_indicators keyword search over ~1,210 dataflows (paginated by offset) local catalogue (no upstream call)
ilo_get_indicator_metadata dimensions, codelists, vintage and default selection of a dataflow cached structure (miss → upstream)
ilo_list_dimension_values valid codes of one dimension (paginated by offset) cached codelist (miss → upstream)
ilo_get_data observations filtered by dimension and period 1 live REST call per query

Typical flow: ilo_search_indicatorsilo_get_indicator_metadata / ilo_list_dimension_values to discover valid filter codes → ilo_get_data with country and period filters.

Every response carries the provenance block v1.0 (@sbissoli/mcp-provenance, modes concise/detailed via the provenance_mode parameter) on three channels: structuredContent, namespaced _meta (com.sidneybissoli.ilostat/*) and a text footer.

Resources and prompts

Three resources (static, text/markdown, no upstream call) that a client can attach to the context before calling tools — they save the 2–3 discovery calls most sessions spend on "which dataflow, which codes":

URI Content
ilostat://guide tool workflow, stable code conventions (REF_AREA ISO3 + X-aggregates, SEX, AGE, FREQ, dataflow id suffixes), limits, reporting rules
ilostat://reference/key-dataflows verified dataflow ids by topic (unemployment, employment, participation, wages, hours, informality, NEET, SDG 8, productivity)
ilostat://reference/provenance meaning of every provenance field and how to cite the ILO

Three prompts — ready-made workflows that chain the tools and end with the citation rules (arguments are strings; period arguments optional):

Prompt Arguments Result
ilo_country_labour_profile country, start_period, end_period labour-market profile of one country (unemployment, participation, employment ratio, informality, NEET, earnings, hours)
ilo_compare_countries countries, indicator, start_period, end_period comparison table across countries/aggregates in one data call, flagging modelled estimates vs reported data
ilo_indicator_trend indicator, country, start_period, end_period time series of one indicator with first/last, peak/trough and OBS_STATUS breaks

Every dataflow id quoted in the resources and prompts is checked against the catalogue seed by the test suite, so the documentation cannot point at an id the search would not find.

Behaviour and limits

  • REF_AREA is required in ilo_get_data, up to 30 areas per call. The ILO gateway times out (HTTP 504) on unrestricted queries, so the server never issues one; for broad panels, split the areas into batches and/or paginate by period (start_period/end_period). The error message explains how.
  • One live REST call per data query. Data is never cached — every ilo_get_data result is fetched from ILOSTAT at request time. Dataflow structures (TTL 24 h) and codelists (TTL 7 days, shared across dataflows) are cached.
  • data_vintage is the dataflow's last-update date as published by the ILO (LAST_UPDATE annotation, normalised to ISO).
  • retrieved_at is always the real instant of extraction from ILOSTAT, preserved alongside any cached value — never the build or response time. Cached responses say so (served_from_cache: true).
  • The indicator catalogue is a local snapshot (~1,210 dataflows), refreshed periodically; its own retrieved_at is reported in the provenance of ilo_search_indicators, so its age is always visible.
  • Every upstream call carries an identifiable User-Agent (service URL + contact), so ILO administrators can reach the operator.
  • Language: English; timezone: UTC (ILO data is published in English).

Provenance fields

  • derivedtrue only for real transformation (aggregation, server-computed rate, interpolation, harmonisation), always with a derivation_note; unit conversion and rounding do not count. This server does not transform values, so derived is always false.
  • notices — reproduces the values of OBS_STATUS (the SDMX status/disclaimer channel, e.g. "Break in series"), verbatim and with counts. Technical per-observation attributes (DECIMALS etc.) stay on the rows (rows[].attributes).

Data license and attribution

  • ILOSTAT data and metadata: CC BY 4.0 (since 2023-05-03; license verified 2026-08-04).
  • ILO attribution in every response (citation field): International Labour Organization, ILOSTAT, https://ilostat.ilo.org/data/, accessed <date>.
  • The ILO logo is not used. This service is not endorsed by the ILO.

Self-hosting / development

Everything below is only needed to run your own instance — it is not required to use the public server.

npm install
npm run typecheck && npm test   # 96 offline tests (parsers, key, tools, output contract, resources/prompts, in-memory catalogue, eval fixtures)
npm run dev                     # http://localhost:8787/mcp (Worker)
npm run build && npm start      # stdio runtime (dist/cli.js)

# Catalogue seed (D1) — required before first use:
node scripts/seed-catalog.mjs   # downloads via curl and generates scripts/seed-catalog.sql
npx wrangler d1 execute ilostat-catalog --local  --file=scripts/seed-catalog.sql
npx wrangler d1 execute ilostat-catalog --remote --file=scripts/seed-catalog.sql

npm run deploy
node scripts/smoke-mcp.mjs      # smoke test against production (initialize → 4 tools → errors)
npm run manifest:lhm            # regenerate tools/resources/prompts in lhm.plugin.json from the real server
# (the seed also writes tests/fixtures/catalog-ids.txt — the versioned id list the tests check resources/prompts against)

Bindings (see wrangler.jsonc): KV SDMX_CACHE, D1 CATALOG_DB, Durable Object USAGE (SQLite-backed usage counters), CF_VERSION_METADATA. Optional Bearer auth (wrangler secret put API_KEY); token-bucket rate limit per IP.

Notes for operators:

  • ILOSTAT returns JSON only when negotiated via the Accept header (application/vnd.sdmx.{structure,data}+json); ?format= is ignored and returns XML.
  • The ILO gateway answers HTTP 500 (languageTag1) to the Accept-Language: * header that Node's fetch (undici) sends by default; every upstream call therefore sets Accept-Language: en explicitly (Cloudflare's runtime sends no such header, so the Worker was never affected). It also expects an identifiable User-Agent.
  • Catalogue refresh is manual (no cron): quarterly, or immediately if a dataflow that exists upstream does not show up in search. Procedure: the three seed commands above. Data queries are always live, so only the search catalogue can age — and its age is exposed in provenance.

Evals

@sbissoli/mcp-evals: 24 fixtures in evals/fixtures/queries.ts, validated offline in npm test. The run with a real model (npm run eval) uses the Anthropic API and needs ANTHROPIC_API_KEY (without it, it exits with instructions). Run of 2026-08-07: top-1 100% (24/24)evals/results/.

End-to-end: 10 complex questions with a single verifiable answer in evals/e2e/evaluation.xml, answers validated manually against production (evals/e2e/validacao-respostas.md). Run of 2026-08-07 (Sonnet): 9/10 exact string; 10/10 substantiveevals/results/2026-08-07-e2e.md.

Endpoints

Route Purpose
/ landing page (service identity + contact — public)
/health liveness
/status version, tool/resource/prompt counts and names, provenance contract version, current deploy (feeds the README badges)
/metrics aggregated usage (MCP endpoint only; no IPs, no query content)
/mcp MCP Streamable HTTP

Security

Snyk Agent Scan (2026-08-07): passed — report in security/.

License

Code: MIT. Data: ILOSTAT, CC BY 4.0 (see "Data license and attribution" above).

Privacy

Privacy policy of the hosted service: PRIVACY.md.

Contact

Sidney da S. P. Bissoli — [email protected]. This service is not endorsed by the ILO.

from github.com/SidneyBissoli/ilo-mcp-server

Installing ILO Statistics (ILOSTAT) Server

This server has no published package — it is built from source. Open the repository and follow its README.

▸ github.com/SidneyBissoli/ilo-mcp-server

FAQ

Is ILO Statistics (ILOSTAT) Server MCP free?

Yes, ILO Statistics (ILOSTAT) Server MCP is free — one-click install via Unyly at no cost.

Does ILO Statistics (ILOSTAT) Server need an API key?

No, ILO Statistics (ILOSTAT) Server runs without API keys or environment variables.

Is ILO Statistics (ILOSTAT) Server hosted or self-hosted?

A hosted option is available: Unyly runs the server in the cloud, no local setup required.

How do I install ILO Statistics (ILOSTAT) Server in Claude Desktop, Claude Code or Cursor?

Open ILO Statistics (ILOSTAT) Server on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.

Related MCPs

Compare ILO Statistics (ILOSTAT) Server with

Not sure what to pick?

Find your stack in 60 seconds

Author?

Embed badge for your README

Browse similar

All data MCPs