Skip to main content
Glama

Related Servers

Alternatives to IBGE Brasil MCP

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that enables querying detailed address information from Brazilian postal codes (CEPs) via the ViaCEP API, returning data such as street names, neighborhoods, cities, states, regions, and IBGE codes.
    1
    2
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that connects AI assistants to Brazilian public data services, providing access to postal codes, company registrations, bank information, area codes, IBGE data, currency exchange rates, and domain registration status.
    11
    8 npm
    4
    MIT

Related Servers

  • A
    license
    A
    quality
    C
    maintenance
    An MCP server that connects AI agents to over 200 tools across 27 Brazilian public APIs, covering economic, legislative, transparency, and judicial data. It enables users to query and cross-reference extensive government datasets from sources like IBGE, the Central Bank, and the Brazilian Congress.
    7
    1,807
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for accessing IBGE (Brazilian Institute of Geography and Statistics) data, enabling natural language queries via the Pipeworx gateway.
    28 npm
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    MCP Server for accessing 36 Brazilian public data sources and 1 agent, enabling AI agents to query government data on economy, legislation, transparency, judiciary, elections, environment, health, and more.
    6
    MIT

TDQS

A4.4/5.0

Scored across 23 tools

Disambiguation4/5

Most tools target clearly distinct resources (localities, census, news, calendar, CNAE, countries), and descriptions include explicit 'Use a different tool when' guidance that resolves overlaps. However there is real conceptual overlap among the SIDRA wrappers (ibge_censo, ibge_indicadores, ibge_cidades, ibge_comparar, ibge_datasaude) and the low-level ibge_sidra, so an agent could still misselect on an ambiguous query.

Naming Consistency4/5

Nearly all tools use a consistent ibge_ snake_case prefix with Portuguese resource/action names (ibge_municipios, ibge_estados, ibge_comparar, ibge_geocodigo). The only deviations are 'search' and 'fetch', which are deliberately named to satisfy the OpenAI Deep Research contract, a minor and justified exception.

Tool Count4/5

23 tools is on the heavy side, but the domain is extremely broad (geography, census, time series, health, news, calendar, CNAE, countries, meshes, names) and a layered low-level-plus-wrapper design is intentional. Each tool maps to a distinct resource or workflow, so the count is justified though bordering on large.

Completeness5/5

The surface covers an impressively wide range: locality lookup, geocoding, administrative and thematic meshes, census/indicator/health wrappers, the raw SIDRA engine with table discovery and metadata, news, calendar, CNAE, names, countries, and comparison. Lifecycle operations (find table -> metadata -> query, name->code->details) are all present with no obvious dead ends.

Maintenance

ActivityActive
ResponsivenessSlow