gov-data-mcp
Related Servers
Alternatives to gov-data-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP 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
- FlicenseAqualityCmaintenanceAn 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-
- AlicenseAqualityDmaintenanceMCP Server for accessing 36 Brazilian public data sources and 1 agent, enabling AI agents to query government data on economy, legislation, transparency, judiciary, elections, environment, health, and more.6MIT
- AlicenseBqualityDmaintenanceMCP server providing AI agents with access to German government open data. 12 tools across 6 categories: Autobahn traffic, DWD weather, NINA disaster warnings, SMARD energy market, Bundestag parliamentary data, and pollen forecasts. All APIs are free, no keys required.162MIT
- AlicenseAqualityCmaintenanceMCP 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.1147 npmMIT
- AlicenseAqualityCmaintenanceAn 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.71,785MIT
TDQS
Scored across 15 tools
Most tools have clearly distinct domains, and the environmental due-diligence tools explicitly cross-reference one another with 'choose this for X, not Y' guidance. There is still some residual overlap between site-due-diligence-bundle and the individual EPA/wetlands/NHD screeners, so an agent must read descriptions carefully to avoid misselection.
All tool names use consistent kebab-case, with no camelCase or underscore mixing. The naming is not a uniform verb_noun pattern because domain tools are noun phrases while the three meta tools use verb prefixes, but it is predictable and readable.
15 tools is within a reasonable range for a broad government-data gateway with both dedicated workflows and catalog meta-tools. The count is slightly heavy because several environmental screeners are narrow and related, but each still has a defensible purpose.
The search -> describe -> run meta-tools provide access to a 122-tool catalog, so the server has a complete read-only lifecycle for discovering, shaping, and executing government-data queries. The dedicated tools cover common verticals, and no obvious operational dead end is present for the stated read-only purpose.