Provenance-first MCP server for ILOSTAT (ILO labour statistics) — remote, Cloudflare Workers
- ✓Open-source license (MIT)
- ✓Actively maintained (<30d)
- ✓Clear description
- ✓Documented (README)
claude mcp add ilo -- npx -y wrangler{
"mcpServers": {
"ilo": {
"command": "npx",
"args": ["-y", "wrangler"]
}
}
}Resumen de MCP Servers
# ILO Labour Statistics (ILOSTAT) — MCP Server

[](https://github.com/SidneyBissoli/ilo-mcp-server/actions/workflows/ci.yml)
[](https://ilo.sidneybissoli.com/status)
[](https://ilo.sidneybissoli.com/status)
[](https://ilo.sidneybissoli.com/status)
[](https://ilo.sidneybissoli.com/status)
[](https://www.npmjs.com/package/ilo-mcp-server)
[](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.SidneyBissoli%2Filo-mcp-server/versions)
[](https://glama.ai/mcp/servers/SidneyBissoli/ilo-mcp-server)
[](LICENSE.md)
[](https://ilo.sidneybissoli.com/status)
🇧🇷 [Leia em Português](README.pt-BR.md)
A **public, hosted, provenance-first** [MCP](https://modelcontextprotocol.io) 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.
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:
```json
{
"mcpServers": {
"ilostat": {
"url": "https://ilo.sidneybissoli.com/mcp"
}
}
}
```
For clients that launch MCP servers as a command, use the
[`mcp-remote`](https://www.npmjs.com/package/mcp-remote) bridge:
```json
{
"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`](https://www.npmjs.com/package/ilo-mcp-server), Node ≥ 20):
```json
{
"mcpServers": {
"ilostat": {
"command": "npx",
"args": ["-y", "ilo-mcp-server"]
}
}
}
```
Or from source:
```bash
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_indicators` → `ilo_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`](https://www.npmjs.com/package/@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
- **`derived`** — `true` 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.
```bash
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-cataloLo que la gente pregunta sobre ilo-mcp-server
¿Qué es SidneyBissoli/ilo-mcp-server?
+
SidneyBissoli/ilo-mcp-server es mcp servers para el ecosistema de Claude AI. Provenance-first MCP server for ILOSTAT (ILO labour statistics) — remote, Cloudflare Workers Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-08-19.
¿Cómo se instala ilo-mcp-server?
+
Puedes instalar ilo-mcp-server clonando el repositorio (https://github.com/SidneyBissoli/ilo-mcp-server) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar SidneyBissoli/ilo-mcp-server?
+
Nuestro agente de seguridad ha analizado SidneyBissoli/ilo-mcp-server y le ha asignado un Trust Score de 87/100 (tier: Trusted). Revisa el desglose completo de comprobaciones superadas y flags en esta página.
¿Quién mantiene SidneyBissoli/ilo-mcp-server?
+
SidneyBissoli/ilo-mcp-server es mantenido por SidneyBissoli. La última actividad registrada en GitHub es del 2026-08-19, con 0 issues abiertos.
¿Hay alternativas a ilo-mcp-server?
+
Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.
Despliega ilo-mcp-server en tu cloud
Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.
¿Mantienes este repo? Añade un badge a tu README
Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.
[](https://claudewave.com/repo/sidneybissoli-ilo-mcp-server)<a href="https://claudewave.com/repo/sidneybissoli-ilo-mcp-server"><img src="https://claudewave.com/api/badge/sidneybissoli-ilo-mcp-server" alt="Featured on ClaudeWave: SidneyBissoli/ilo-mcp-server" width="320" height="64" /></a>Más MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
The fastest path to AI-powered full stack observability, even for lean teams.
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!