US Government Open Data MCP
Related Servers
Alternatives to US Government Open Data MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityNot gradedmaintenanceUnified API for Government Data and Web Scraping100-
- AlicenseAqualityAmaintenanceThe most comprehensive keyless federal-data MCP server. 36 tools for SAM.gov + USAspending + Federal Register + eCFR + Grants.gov. No API key, no registration, no signup. Works in Claude Desktop, Claude Code, Codex CLI, Cursor, Continue, Gemini CLI, and any MCP-aware host.6153484 npm9MIT
- AlicenseBqualityDmaintenanceProvides access to 7 free government and open data APIs including NOAA weather, US Census demographics, NASA imagery, World Bank economics, Data.gov, and EU Open Data through 22 specialized tools, with most requiring no API keys.223MIT
- AlicenseBqualityBmaintenance38 AI data tools for Claude and any MCP-compatible agent — crypto, DeFi, equities, commodities, energy, real estate, government intelligence, security audits, and more.45MIT

LoneStarOracle MCP Serverofficial
AlicenseNot gradedqualityFmaintenance38 AI data tools for Claude and any MCP-compatible agent covering crypto, DeFi, equities, commodities, energy, real estate, government intelligence, security audits, and more.MIT- AlicenseBqualityCmaintenanceQuery 20 structured datasets from AI agents — healthcare providers (9M NPI records), SEC EDGAR filings, PACER federal courts, USPTO patents and trademarks, OFAC sanctions screening, crypto whale wallets, DeFi liquidation signals, Polymarket smart money, economic indicators (FRED/BLS), federal contracts, NOAA weather, and OTC shell risk scoring. Pay per query, no subscriptions751MIT
TDQS
Scored across 345 tools
The tool set spans dozens of agencies and domains, and while many tools are domain-specific, there are numerous overlapping tools within domains (e.g., congress_bill_details vs congress_bill_full_profile, epa_air_quality vs epa_aqs_daily, fda_device_enforcement vs fda_device_recalls, nhtsa_recalls vs nhtsa_recall_detail, multiple 'search' vs 'query' tools). The sheer scale and redundant 'full profile' convenience tools create significant ambiguity about which tool to select.
Most tools follow a consistent agency_prefix + noun + verb pattern (e.g., congress_search_bills, fda_drug_events, nws_forecast), but there are notable deviations: 'code_mode' and 'clear_cache' break the pattern, some tools use inconsistent verb placement (e.g., 'search_datasets' vs 'list_datasets' vs 'get_endpoint_fields'), and the 'full_profile' tools mix conventions. Overall readable but not uniform.
345 tools is an extreme count for a single MCP server. Even though it aggregates many government data sources, the server would be far more usable split into per-agency servers. The count is far beyond what an agent can effectively navigate, and many tools are redundant convenience wrappers.
The server covers an impressively broad range of government data domains, and many domains have reasonable search/detail coverage. However, completeness is uneven: some domains have deep coverage (Congress, FDA, EPA) while others are thin (e.g., only a few CDC tools, no update/delete operations since this is read-only data). The 'query' tools partially fill gaps, but the overall surface is more broad than systematically complete.