Skip to main content
Glama
cyntrica

Gov Data MCP

by cyntrica
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Gov Data MCP

No user-submitted related servers found.

    Related Servers

    • Data.gov MCP Server

      melaodoidao
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides access to government datasets from Data.gov, enabling users to search packages, view dataset details, list groups and tags, and access resources by URL.
      4
      27 npm
      19
      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
      101 npm
      MIT

    • mcp-brasil

      Mcp-Brasil
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that connects AI agents to over 200 tools across 27 Brazilian public APIs, covering economic, legislative, transparency, and judicial data. It enables users to query and cross-reference extensive government datasets from sources like IBGE, the Central Bank, and the Brazilian Congress.
      7
      1,777
      MIT

    • ausdata-mcp

      Bigred97
      A
      license
      A
      quality
      F
      maintenance
      Cited Australian stats via the ausdata.io gateway — stable AU.* series IDs, source_url + retrieved_at on every response. Free tier. Not a data broker; upgrade for Embed / signed / webhooks.
      28
      76 npm
      2
      MIT

    • mcp-brasil

      davidlustosa2
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI agents to 28 Brazilian public APIs, providing tools to query government data on economy, legislation, transparency, judiciary, elections, environment, health, and more.
      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 563 tools

    Disambiguation2/5

    Generic tools like `transit_arrivals`, `cdc_query`, `census_query`, `epa_air_quality`, and `fda_count` overlap with system-specific or endpoint-specific tools (`bart_departures`, `cdc_mortality_rates`, `epa_aqs_daily`, `fda_drug_counts`), making boundaries unclear. Congress `*_full_profile` bundle tools also duplicate their constituent detail tools. With 563 tools, an agent has no clear rule for choosing among several near-equivalent options.

    Naming Consistency3/5

    Most tools use a `<source>_<action>` pattern (e.g., `nws_forecast`, `fda_drug_events`, `congress_bill_details`), which makes the set readable overall. However, verb/noun ordering is inconsistent (`cfpb_search_complaints` vs `cfpb_complaint_detail`), and several tools break the prefix pattern (`list_datasets`, `get_endpoint_fields`, `clear_cache`, `code_mode`). The mixed conventions are still navigable but far from uniform.

    Tool Count1/5

    With 563 tools, this server is an extreme mismatch for a single MCP server; it aggregates dozens of independent government APIs with no apparent scoping. Even if each tool is individually useful, the combined surface is unmanageable for coherent agent selection and tool-choice reasoning.

    Completeness4/5

    The server covers most major U.S. government data areas — Congress, FDA, EPA, labor, energy, climate, transit, courts, and spending — and includes generic query tools that help fill gaps. Missing pieces such as full court docket/filing search or detailed tax records are minor relative to the enormous scope covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources