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
- FlicenseAqualityDmaintenanceAn 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.163MIT
- 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.1137 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,809MIT
TDQS
Scored across 15 tools
Each dedicated tool targets a distinct data domain (airspace, grid, wetlands, drinking water, parcels, licenses, etc.), and the descriptions actively disambiguate the few adjacent pairs (bundle vs. contaminated-site screener, FWS wetlands vs. NHD surface water, drinking water vs. site contamination) with explicit 'CHOOSE THIS' / 'use X instead' guidance. The meta trio (search/describe/run) is clearly framed as the fallback path for anything not covered by the dedicated tools, so no two tools appear to do the same thing.
All names are kebab-case and readable, and the 12 dedicated tools follow a consistent agency/topic-plus-role pattern (-screener, -checker, -tracker, -rollup, -profile, -lookup, -verifier, -bundle). The three meta tools, however, switch to a verb_noun convention (search-/describe-/run-gov-data-tool), leaving two naming families in one set.
15 tools sits at the top of the well-scoped band but is justified: 12 curated high-frequency domain tools plus 3 meta tools that expose the remaining 111 catalog entries. No tool appears redundant or vestigial for the server's stated purpose.
The search/describe/run trio provides full reach into the 123-tool catalog, and describe-before-run plus local input validation removes dead ends, while the dedicated tools cover the most common government-data workflows (environmental, energy, water, parcels, licensing, financial health). No obvious lifecycle gap exists for a read-only data-lookup server.