Skip to main content
Glama
EricGrill

Civic Data MCP Server

by EricGrill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Civic Data MCP Server

No user-submitted related servers found.

    Related Servers

    • US Government Open Data MCP

      lzinga
      A
      license
      B
      quality
      A
      maintenance
      MCP server + TypeScript SDK for 36 U.S. government data APIs — 188 tools. Treasury, FRED, Congress, FDA, CDC, FEC, lobbying, and more. Works with VS Code Copilot, Claude Desktop, Cursor.
      345
      174 npm
      110
      MIT

    • MCP Public Data

      fat-operator
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying, sampling, and exporting datasets from over twenty keyless free public data sources spanning the EU, Switzerland, Germany, the US, and global providers through one uniform set of tools. A single consistent interface lets users list databases and tables, inspect schemas and query guides, run queries, and export results as CSV or JSON without per-API clients.
      Apache 2.0

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

    • Gov Data MCP

      cyntrica
      A
      license
      B
      quality
      D
      maintenance
      MCP server with 562 tools accessing 114 government data APIs covering economic, health, education, energy, and more from federal, state, and international sources.
      4
      100
      101 npm
      1
      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.1/5.0

    Scored across 22 tools

    Disambiguation3/5

    Tools are grouped by data source and purpose, but there is significant overlap. For example, get_country_indicators and compare_countries both use World Bank data, and get_weather_forecast and get_global_weather both provide weather information. Descriptions help clarify, but an agent might struggle to choose between overlapping tools like query_nasa and get_astronomy_photo.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., get_country_indicators, search_datasets, query_census). However, there are minor deviations, such as compare_countries (verb_noun but not 'get' or 'query') and get_astronomy_photo (abbreviated 'photo' instead of 'picture'). Overall, the naming is readable and predictable.

    Tool Count2/5

    With 22 tools, the count feels heavy for a 'Civic Data' server, as it spans multiple unrelated domains like astronomy, Mars photos, and global weather. This suggests a lack of focus; a more cohesive set might have 10-15 tools centered on government or economic data. The broad scope makes the toolset overwhelming and less coherent.

    Completeness3/5

    For each data source (e.g., World Bank, NASA, NOAA), there is basic coverage with get/search/query tools, but gaps exist. For instance, there are no update or delete operations, which is reasonable for read-only data, but some domains lack comprehensive endpoints (e.g., limited NASA tools beyond APOD and images). The surface is functional but not fully rounded for all implied use cases.

    Maintenance

    ActivityInactive
    ResponsivenessSlow

    Resources