Skip to main content
Glama
ONSdigital

Statistics Query and Verification MCP

Official
by ONSdigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Statistics Query and Verification MCP

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

    • mcp-ssb-no

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Statistics Norway (SSB) PxWebApi, enabling table metadata queries via a single tool.
      2 npm
      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
      35 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
      59 npm
      MIT

    • mcp-stat-lv

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables querying Latvian official statistics from data.stat.gov.lv via PxWeb tables, allowing retrieval of table definitions and data through natural language or direct tool calls.
      3 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

    B3.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: validation, overview, text retrieval, data file retrieval, and search. There is no overlap in functionality, and the descriptions reinforce the boundaries.

    Naming Consistency4/5

    All tool names use snake_case and a verb-object structure, but there is a minor inconsistency: three tools use the 'get_publication_*' prefix, while 'get_data_file' omits 'publication' and 'search_publication' uses a different object. This is a slight deviation from a fully uniform pattern.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its stated purpose of querying and verifying statistics in a publication. Each tool contributes a necessary function without redundancy or bloat.

    Completeness4/5

    The core workflow of validating, retrieving metadata, fetching text and data, and searching is covered. A minor gap is the lack of a direct tool to fetch specific sections or subsets of a data file beyond the full file, but the search tool partially mitigates this.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources