Skip to main content
Glama
SidneyBissoli

ILO Statistics (ILOSTAT) MCP Server

by SidneyBissoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ILO Statistics (ILOSTAT) MCP Server

Related Servers

  • ilostat-mcp-server

    cyanheads
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables searching ILOSTAT labour indicators, querying and comparing series, building country profiles, and running read-only SQL over staged dataframes via MCP.
    114 npm
    1
    Apache 2.0

  • UNESCO UIS Education

    SidneyBissoli
    A
    license
    A
    quality
    A
    maintenance
    Remote MCP server for the UNESCO Institute for Statistics (UIS): ~5,000 indicators on education, science/R&D, culture and communication by country, region and year — hosted, nothing to install, no API key, with source URL, data release, retrieval timestamp and licence on every answer.
    5
    84 npm
    1
    MIT

  • @nor-data/statfin-mcp

    3121n
    A
    license
    A
    quality
    D
    maintenance
    MCP server for official statistics from Statistics Finland (Tilastokeskus) — the StatFin database, exposed through the PxWeb API. Search 3000+ tables, inspect their dimensions, and pull data as JSON-stat2.
    4
    33 npm
    MIT

  • starwell-mcp

    Adarsh4052
    A
    license
    A
    quality
    C
    maintenance
    MCP server serving official statistics from major data agencies (Statistics Canada, FRED, BLS, World Bank, etc.) as tools with provenance and verification, enabling search, retrieval, analysis, and monitoring via natural language.
    11
    57 npm
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 6 tools

Disambiguation4/5

The four ilo_* tools have clearly distinct roles across discovery, metadata, dimension lookup, and data retrieval, and the descriptions explicitly separate them. The main ambiguity is between ilo_search_indicators and search, and between ilo_get_data and fetch, but the descriptions strongly redirect agents to the correct tool for data versus documents.

Naming Consistency4/5

The ilo_* tools consistently follow a verb_noun snake_case pattern: ilo_search_indicators, ilo_get_indicator_metadata, ilo_list_dimension_values, ilo_get_data. The unprefixed search and fetch tools are a deliberate contract exception, but they are still readable and do not use a conflicting style.

Tool Count5/5

Six tools is well-scoped for an ILOSTAT data access server, covering the full discovery-to-retrieval workflow without unnecessary surface area. Each tool earns its place, including the separate search/fetch pair required by the Deep Research contract.

Completeness4/5

The surface covers the core lifecycle: find indicators, inspect metadata, resolve dimension codes, and retrieve observations, with search/fetch for document retrieval. Minor gaps remain, such as no direct way to check which dimension codes actually have data for a given dataflow, but agents can work around this through trial queries.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources