{"id":"lzinga-us-gov-open-data-mcp","name":"us-gov-open-data-mcp","af_score":77.0,"security_score":60.0,"reliability_score":31.2,"what_it_does":"Provides an MCP server (via stdio and HTTP Stream) and a TypeScript SDK that expose 300+ tools across 40+ U.S. government (and some international) open-data APIs, with module-level selective loading, disk-backed caching, and built-in rate limiting/retry.","best_when":"You want broad coverage of U.S. government APIs accessible to AI agents or typed code, with caching and rate-limit handling, and you can supply any needed upstream API keys via environment variables.","avoid_when":"You need a standardized single REST/OpenAPI contract for all tools, strict enterprise security controls (e.g., no local process execution), or strong guarantees about per-endpoint schema correctness beyond the stated community/accuracy caveats.","last_evaluated":"2026-03-30T13:48:17.002887+00:00","has_mcp":true,"has_api":false,"auth_methods":["Environment variable API keys for upstream APIs (e.g., FRED_API_KEY, DATA_GOV_API_KEY)"],"has_free_tier":false,"known_gotchas":["Large number of tools (300+) increases the chance an agent calls an endpoint with mismatched parameters/schema; the README warns about incomplete parameter coverage/unexpected endpoint behaviors.","Some APIs require keys; missing/invalid env vars may cause tool failures.","Because selective loading exists, agents may need to ensure the relevant modules are enabled for the tools they intend to call.","Local npx execution and disk-backed caching may create environment-specific behavior (permissions/path) if running under constrained desktops/containers."],"error_quality":0.0}