Skip to main content
Glama
lbruce-wq

Development Indicators MCP

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Development Indicators MCP

No user-submitted related servers found.

    Related Servers

    • World Bank MCP Server

      anshumax
      F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with the World Bank open data API, allowing for listing and analysis of indicators across available countries.
      1
      50
      -

    • WHO MCP Server

      openpharma-org
      A
      license
      B
      quality
      D
      maintenance
      Provides access to the World Health Organization's Global Health Observatory data, enabling AI assistants to search, retrieve, and analyze comprehensive health indicators, country statistics, disease burden data, and regional health trends through WHO's OData API.
      1
      MIT

    • World Bank Data360 MCP Server

      llnOrmll
      A
      license
      A
      quality
      D
      maintenance
      Enables access to World Bank Data360 API with 1000+ economic and social indicators across 200+ countries and 60+ years of historical data, allowing searches, temporal coverage checks, and filtered data retrieval through natural language queries.
      5
      1
      MIT

    • mcp-unicef

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides access to UNICEF data on global statistics about child health, enabling AI agents to query child health indicators.
      5 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

    A3.5/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing sources, retrieving setup details, finding microdata, searching indicators, FAOSTAT-specific queries, geography resolution, metadata retrieval, observation retrieval, and comparison. Descriptions clearly differentiate overlapping areas like list_sources vs find_microdata.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., list_sources, get_observations, compare_observations). Prefixing FAOSTAT-specific tools with 'faostat_' adds a clear namespace without breaking the pattern.

    Tool Count5/5

    With 10 tools, the server is well-scoped for discovering, searching, and retrieving development indicator data. This count is within the ideal range and each tool earns its place by covering a distinct part of the workflow.

    Completeness4/5

    The surface covers the full discovery-to-retrieval pipeline: source enumeration, search, metadata, observations, and comparison. Minor gaps exist (e.g., no bulk download or time-series filtering), but these are not severe dead ends for typical use cases.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources