Data.gov MCP Server
Related Servers
Alternatives to Data.gov MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools to search, query, and aggregate data from any Socrata open data portal.-
- AlicenseNot gradedqualityBmaintenanceMCP server for accessing data.ny.gov datasets via the Socrata Open Data API, enabling search, query, metadata retrieval, and column value exploration.6 npm1MIT
- AlicenseBqualityDmaintenanceMCP server with 562 tools accessing 114 government data APIs covering economic, health, education, energy, and more from federal, state, and international sources.4100164 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for the Moroccan Open Data portal (data.gov.ma) enabling search and retrieval of datasets, resources, organizations, and groups via CKAN API.1MIT
- AlicenseAqualityBmaintenanceMCP server for searching and accessing Korean public data from data.go.kr, enabling dataset search, metadata lookup, and data retrieval/download via Python API or CLI.926 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query U.S. government datasets via the Data.gov CKAN API, wrapped as an MCP server.6 npmMIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose targeting different resources: groups, packages (datasets), and tags. The actions (list, search, show) are well-defined and non-overlapping, making it easy for an agent to select the right tool without confusion.
All tool names follow a consistent snake_case pattern with a clear verb_noun structure (e.g., group_list, package_search). This predictability enhances readability and usability across the tool set.
With only 4 tools, the set feels thin for a data portal server, lacking operations like create, update, or delete for resources. While the tools cover basic read/search functions, the scope could be expanded for more comprehensive coverage.
The tool surface is severely incomplete for a data management domain, missing essential CRUD operations (e.g., no create_package, update_package, delete_package) and other common actions like resource_show for groups or tags. This will likely cause agent failures when trying to perform full lifecycle tasks.