Skip to main content
Glama

Ibge Br

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

IBGE (Instituto Brasileiro de Geografia e Estatística) MCP.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
33.5% over 50 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-ibge-br
GitHub Stars
0
Server Listing
mcp-ibge-br

TDQS

A3.8/5.0

Scored across 37 tools

Disambiguation2/5

The set contains blatant duplicates and near-duplicates: ask_pipeworx, ask_pipeworx_beta (advertised as identical right now), and ask_pipeworx_grounded all do the same routing, and scan_competitor_ai_presence merely wraps ai_visibility_check. The six polymarket_* tools plus bet_research overlap heavily (edges vs arbitrage vs fill_risk vs kalshi_spread all reason about the same markets), so an agent must read long descriptions to pick correctly.

Naming Consistency4/5

Everything is snake_case with a predictable verb_noun or noun_phrase shape (list_states, lookup_municipality, aggregated_data, polymarket_fill_risk), and the _beta/_grounded suffixing is systematic. It is not a perfect verb_noun monoculture (aggregated_data, name_frequency, entity_profile are noun phrases), but the pattern is readable and consistent.

Tool Count2/5

37 tools is well past the point of being scoped; for a server named 'Ibge Br' only six tools (aggregated_data, list_aggregates, list_states, list_municipalities, lookup_municipality, name_frequency) belong. The remaining 31 are a general Pipeworx data/router/subscription/memory/prediction-market toolkit bolted onto an IBGE server.

Completeness3/5

The IBGE/SIDRA surface itself is decent (aggregate catalog + series pull + state/municipality listing and lookup + name statistics), but it lacks discovery helpers for variables, periods, and localities, forcing callers to guess ids for aggregated_data. The overall surface is broad but incoherent, mixing unrelated domains rather than covering one completely.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources