Make HTTPS calls to the specific federal APIs listed in each server's readme (SAM.gov, BLS, GSA, USASpending, api.data.gov, eCFR, Federal Register, Regulations.gov). Nothing else.
Read API keys from environment variables or config env blocks supplied by your MCP client.
Return structured query results back to your MCP client for you to reason over.
Log errors to stderr, visible through your MCP client's debug output.
Ship with full source on GitHub, a testing.md audit record per server, and MIT license for modification.
These MCPs DO NOT
Read any files on your computer. The servers have no file I/O to your disk.
Access your chat history, memory, or conversation context outside the tool arguments your MCP client passes in.
Send telemetry, usage data, or analytics anywhere. No third-party calls other than the federal APIs above.
Store your queries, API keys, or responses anywhere outside your local machine and local client config.
Modify any system settings, install software, or persist beyond the MCP client process that spawned them.