{"id":"jxnxts-mcp-brasil","name":"mcp-brasil","homepage":null,"repo_url":"https://github.com/jxnxts/mcp-brasil","category":"devtools","subcategories":[],"tags":["mcp","python","ai-agents","government-data","brasil","public-apis","fastmcp","tool-discovery","batch-execution"],"what_it_does":"mcp-brasil is a Python MCP server that exposes a large catalog of Brazilian public-data APIs (41 features, 326 tools) to AI agents via MCP. It includes meta-tools for smart discovery (BM25/code-mode), cross-referencing/planning across multiple APIs, and parallel batch execution. Some underlying APIs support optional API keys; the README claims most tools work without keys.","use_cases":["Connect LLM/MCP clients to Brazilian government/public datasets (economic indicators, legislation, transparency, judiciary, elections, health, public safety, environment).","Multi-API research workflows (e.g., plan and cross-reference spending + votes + propositions).","Automated batch querying of many entities/time ranges via a single MCP call.","Discovery of relevant tools based on natural-language context to reduce tool-selection overhead."],"not_for":["Writing/transforming government data into authoritative outputs (the server is described as a proxy to upstream APIs, not an editor).","Environments requiring guaranteed data freshness/consistency beyond what upstream APIs provide.","Use cases needing formal SLAs, audited reliability guarantees, or strong contractual uptime."],"best_when":"You want an MCP-compatible integration to quickly access many Brazilian open/government APIs from an agent, with minimal setup and built-in tool discovery/planning.","avoid_when":"You require strict idempotency guarantees, detailed error-code semantics, or you cannot tolerate inconsistent upstream API behaviors/parameter coverage.","alternatives":["BrazilAPI + direct REST calls to specific government datasets (build your own orchestration layer).","Other MCP servers focused on a smaller curated set of APIs (feature-by-feature rather than broad catalogs).","Direct SDK/wrappers for a subset of providers (e.g., IBGE, Bacen) depending on your target domains."],"af_score":71.5,"security_score":59.8,"reliability_score":38.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:25:45.237044+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Environment variables for specific upstream APIs (e.g., TRANSPARENCIA_API_KEY, DATAJUD_API_KEY, META_ACCESS_TOKEN)"],"oauth":false,"scopes":false,"notes":"README states keys are optional: without them, remaining APIs should function for 36 tools; 3 use keys (free registration). Auth is configuration via env vars/Claude/Desktop or .vscode JSON."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No product pricing described; it is an open-source server integrating third-party government APIs. Any costs would be indirect (compute and any upstream API charges, if applicable)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":71.5,"security_score":59.8,"reliability_score":38.8,"mcp_server_quality":82.0,"documentation_accuracy":78.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":90.0,"rate_limit_clarity":50.0,"tls_enforcement":85.0,"auth_strength":60.0,"scope_granularity":20.0,"dependency_hygiene":65.0,"secret_handling":70.0,"security_notes":"Security assessment is limited to README/manifest claims. The server is configured via environment variables for upstream API keys/tokens (reducing hard-coded secrets). No explicit guidance is provided about logging redaction, secure storage, or safe handling of tokens beyond env usage. Scope granularity is limited because keys are described as per-upstream API keys rather than fine-grained authorization scopes for the MCP server itself. TLS is not explicitly stated in the README, but HTTP client usage implies HTTPS for upstreams is likely; not guaranteed from provided data.","uptime_documented":0.0,"version_stability":55.0,"breaking_changes_history":50.0,"error_recovery":50.0,"idempotency_support":"false","idempotency_notes":"No explicit idempotency guarantees documented for the tools or batch execution. Most operations appear to be read-only queries, but behavior under retries is not specified.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Large tool catalog (326 tools) may increase selection/search cost; use discovery mode/filters where supported.","Upstream APIs may have inconsistent parameter coverage and result variability (the README includes a disclaimer about partial coverage/unexpected results).","Some tools depend on optional upstream API keys; agents may see degraded coverage for those features without keys."]}}