Skip to main content
Glama
nescoffee-create

SDMX MCP Gateway

by nescoffee-create
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to SDMX MCP Gateway

No user-submitted related servers found.

    Related Servers

    • sdmx-data-mcp

      markchweya
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets AI assistants discover and retrieve official statistics from SDMX services, returning actual data observations rather than just query URLs.
      Apache 2.0

    • OECD-Search

      xiaobenyang-com
      A
      license
      B
      quality
      D
      maintenance
      A model Context Protocol (MCP) server that provides comprehensive OECD statistics through the SDMX API, supporting AI assistants and chatbots to query OECD datasets in areas such as economy, health, education, and environment.
      9
      2
      Apache 2.0

    • 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
      48 npm
      MIT

    • statcan-mcp

      arose26
      A
      license
      A
      quality
      C
      maintenance
      MCP server giving LLMs live access to Statistics Canada's full catalogue of 8,200+ data tables via the Web Data Service, with tools to search tables, inspect dimensions, and fetch time series data using plain-language prompts.
      5
      29 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.4/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but several availability-check tools (get_data_availability, get_code_usage, check_time_availability, probe_data_url) overlap in function and could lead to misselection without careful description reading. The descriptions themselves disambiguate well, so the issue is mild.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (get_, list_, check_, find_, compare_, validate_, build_, probe_, suggest_). No mixed conventions or vague verbs like 'process' or 'do_thing'.

    Tool Count4/5

    20 tools is slightly heavy but justified for a comprehensive SDMX gateway covering discovery, structure, availability, query construction, metadata, visualization, and endpoint management. Each tool serves a defined role, though some could arguably be merged.

    Completeness5/5

    The tool surface covers the full SDMX data workflow: discovery (list_dataflows, find_code_usage_across_dataflows), structure inspection, availability checks, query building/validation, URL generation, probing, recovery from empty results, reference metadata, and endpoint management. No obvious dead ends or missing core operations for its stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources