mcp-sam-gov
Related Servers
Alternatives to mcp-sam-gov
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceMCP server for querying SAM.gov federal contract opportunities, providing precise search, retrieval, and attachment tools with full source traceability and explicit abstention when data is absent.5-
- AlicenseAqualityCmaintenanceGovToolsPro MCP Server — an MCP server that gives Claude and other AI clients workflow tools for US federal contractors: go/no-go scoring, incumbent intelligence (USAspending + FPDS), teaming-partner search, recompete prediction, Navy NECO lookup, and SAM.gov solicitation retrieval. It returns synthesized decisions rather than raw data, so contractors and capture teams can triage opportunities d1044 npm2MIT
- AlicenseNot gradedqualityFmaintenanceAn MCP server for the Congress.gov API that consolidates 91 operations into 6 comprehensive legislative tools that can be used by any MCP client (i.e. Claude Desktop), or MCP-compatible AI agent, to query and reason about congressional data.4 npm1JavaScriptMIT
- AlicenseAqualityBmaintenanceA production-quality MCP server that exposes the official eCFR API as structured tools for AI-driven contract compliance, enabling retrieval of relevant Code of Federal Regulations by clauses extracted from contracts.8Academic Free v1.1
- AlicenseAqualityCmaintenanceMCP server for querying US federal contracts and public company financial data from USAspending and SEC EDGAR. Enables searching expiring contracts, screening companies by metrics, and retrieving financial histories.4MIT

USA Spending MCP Serverofficial
FlicenseBqualityDmaintenanceAn MCP server for interacting with the USAspending.gov API, supporting local use with Claude Desktop and cloud deployment with login.gov authentication.310-
TDQS
Scored across 153 tools
The tool set covers many distinct domains, but within each domain there are overlapping tools (e.g., usas_search_awards vs usas_search_individual_awards vs usas_search_awards_by_recipient). Descriptions are detailed enough to differentiate, but the sheer number (153) increases misselection risk, especially when many tools serve similar search patterns across different sources.
Most tools follow a source-prefix + verb/noun pattern (e.g., socrata_discover_datasets, usas_search_awards), but verbs vary (search/get/lookup/fetch) and some tools are noun-first (e.g., cms_dmepos_suppliers, fdic_risk_ratios). This inconsistency can confuse agents about whether a tool is a search, lookup, or fetch operation.
With 153 tools, the count is extreme and far exceeds typical server scopes. Even for a comprehensive government data aggregator, this is unwieldy and likely to overwhelm agents, leading to poor tool selection and performance issues.
The server covers an exceptionally broad domain—federal spending, procurement, compliance, health, environmental, financial, and legal data—with tools for each major area. While there are minor gaps (e.g., deprecated aliases, some missing detail endpoints), the surface is remarkably comprehensive for its scope.