Skip to main content
Glama
jarib

pxweb-mcp

by jarib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to pxweb-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-ssb-no

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

    • mcp-stat-lv

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      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.
      398 npm
      MIT

    • mcp-norges-bank

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for accessing Norges Bank exchange rates and interest rates via SDMX data flows.
      481 npm
      MIT

    • mcp-makstat-mk

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for accessing North Macedonia's official statistics via PxWeb, enabling subject navigation, table metadata retrieval, and data queries.
      390 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.0

    Scored across 6 tools

    Disambiguation4/5

    Tools are mostly separable: search_tables and list_recent_tables both discover tables but use different criteria, and query_table/get_code_list have unique roles. The only mild overlap is get_table_info versus fetch_metadata, where the descriptions distinguish basic overview from detailed query-building metadata.

    Naming Consistency5/5

    All tool names follow the same verb_noun snake_case pattern (search_tables, query_table, get_code_list, etc.). The use of fetch instead of get in fetch_metadata is a minor synonym variation but does not break the overall pattern.

    Tool Count5/5

    Six tools is a well-scoped size for a statistical data server, covering discovery, metadata inspection, code lists, and querying. Each tool has a distinct role and none feels like filler.

    Completeness5/5

    The tool set supports the full user workflow: find tables, inspect metadata, resolve code lists, and query data. For a read-only public statistics API, there are no obvious missing operations that would create dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources