Skip to main content
Glama
hesscl

ipums-mcp

by hesscl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ipums-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-server-eia

      GSA-TTS
      F
      license
      A
      quality
      C
      maintenance
      An MCP server that exposes the U.S. Energy Information Administration (EIA) Open Data API, enabling LLMs to browse and query energy data across 17 datasets with generic, composable tools.
      4
      -

    • census-mcp-server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server to query U.S. Census Bureau data, variables, and geography through 7 tools supporting dataset discovery, variable search, geography resolution, and data queries with suppression code decoding.
      300 npm
      2
      Apache 2.0

    • sodabar

      UsmarHaider
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that puts open data on tap, enabling LLM clients to search, inspect, and query 30,000+ civic datasets from Socrata portals with built-in guardrails like row caps and actionable error messages.
      4
      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
      38 npm
      MIT

    • gov-data-mcp

      malonestar
      A
      license
      A
      quality
      A
      maintenance
      A MCP server exposing 95 US government open-data tools as agent-callable tools, enabling direct access to official APIs for environmental, financial, licensing, and infrastructure data with honest run-status reporting.
      8
      15
      164 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.9/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools have clearly distinct resources and actions, with a consistent list/get/search/create pattern. A few pairs like search_ vs list_ for datasets/tables could be confused, but descriptions clarify the distinction. Overall, only one or two tools have overlapping boundaries.

    Naming Consistency5/5

    All tools follow a consistent prefix (nhgis_ or microdata_) with a verb_noun pattern (list_, get_, search_, create_, download_, wait_for_). Minor exceptions like extract_to_code and generate_ipums_citation are still clear and do not break the overall consistency.

    Tool Count4/5

    23 tools is on the heavier side but justified by covering two substantial domains (NHGIS and IPUMS microdata) with browse, search, extract creation, status, and code generation. The count is slightly over the ideal range but each tool has a clear purpose.

    Completeness3/5

    The microdata workflow is complete: search variables/list samples, create extract, wait, download, generate code. However, the NHGIS side lacks a dedicated download tool (nhgis_get_extract only provides links) and a wait/poll tool analogous to microdata_wait_for_extract, leaving a significant gap for agents that need to fetch NHGIS files programmatically.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources