govbr-apis-mcp
Related Servers
Alternatives to govbr-apis-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to query 153 live Brazilian government data tools across federal and state sources, including economy, legislature, judiciary, elections, health, education, and more, reading directly from original APIs.MIT
- AlicenseAqualityBmaintenanceExposes Brazilian public data — postal codes (CEP), company registrations (CNPJ), CPF/CNPJ validation, banks, national holidays, municipalities, and DDD area codes — as MCP tools and resources, backed by BrasilAPI, ViaCEP, and IBGE with caching, fallback, and rate limiting. Any MCP client such as Claude Desktop or Claude Code can query and validate this reference and registration data through natural language or programmatic calls.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to connect to 28 Brazilian public APIs covering economic, legislative, transparency, judicial, electoral, environmental, health, and other government data, providing 213 tools, 55 resources, and 45 prompts for natural-language queries and cross-referenced analysis.MIT
- AlicenseAqualityCmaintenanceEnables lookup of Brazilian public data including companies (CNPJ), postal codes (CEP), banking, economy, geography, and more through 15 tools and 2 guided prompts, powered by BrasilAPI with no API key required.15MIT
- AlicenseNot gradedqualityNot gradedmaintenanceConnects AI agents to 28 Brazilian public APIs, providing over 200 tools to access data on economy, legislation, transparency, and the judiciary. It enables complex queries and cross-referencing of government datasets like IBGE, the Central Bank, and the National Congress through natural language.MIT
- AlicenseAqualityBmaintenanceEnables LLMs to access Brazilian public data through MCP tools for querying CNPJ, CEP, banks, and national holidays.4MIT
TDQS
Scored across 5 tools
search_catalog and list_apis both enumerate catalog entries and both accept category filters, so their boundary is somewhat blurry (keyword vs. filter is the only real differentiator), though the descriptions do explain the intent. describe_api, credentials_status and call_api each target a clearly distinct facet of the workflow.
Four of five tools follow a clean verb_noun pattern (search_catalog, list_apis, describe_api, call_api). credentials_status breaks it with a noun_noun form, and there is a minor singular/plural mismatch (list_apis vs. describe_api), but overall the naming reads predictably.
Five tools is exactly right for a catalog gateway: one search, one list, one schema lookup, one credential check, one invocation. Each earns its place with no redundancy or padding.
The surface covers the full discover→describe→verify-credentials→call lifecycle, and call_api handles methods, bodies, headers and error/redirect reporting. The only minor gaps are the absence of any way to configure credentials or page through large result sets, both of which an agent can work around.