com.brazilmacro/brazil-macro-ai
REMOTE · API.BRAZILMACRO.COM · SCANNED SEP 29
Brazil Macroeconomic and Financial Data AI Platform for AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3675 tokens (~334/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.brazilmacro/brazil-macro-ai MCP server?
com.brazilmacro/brazil-macro-ai is a hosted endpoint at https://api.brazilmacro.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.brazilmacro.com
claude mcp add --transport http com-brazilmacro-brazil-macro-ai 'https://api.brazilmacro.com/mcp'
{
"mcpServers": {
"com-brazilmacro-brazil-macro-ai": {
"url": "https://api.brazilmacro.com/mcp"
}
}
} {
"servers": {
"com-brazilmacro-brazil-macro-ai": {
"type": "http",
"url": "https://api.brazilmacro.com/mcp"
}
}
} [mcp_servers.com-brazilmacro-brazil-macro-ai] url = "https://api.brazilmacro.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-brazilmacro-brazil-macro-ai": {
"type": "remote",
"url": "https://api.brazilmacro.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-brazilmacro-brazil-macro-ai --url 'https://api.brazilmacro.com/mcp' --transport streamable-http
mcp_servers:
com-brazilmacro-brazil-macro-ai:
url: "https://api.brazilmacro.com/mcp" {
"McpServers": {
"com-brazilmacro-brazil-macro-ai": {
"Transport": "http",
"Url": "https://api.brazilmacro.com/mcp"
}
}
} assistant mcp add com-brazilmacro-brazil-macro-ai -t streamable-http -u 'https://api.brazilmacro.com/mcp'
{
"mcpServers": {
"com-brazilmacro-brazil-macro-ai": {
"type": "http",
"url": "https://api.brazilmacro.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Sept 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://api.brazilmacro.com/mcp/ · Declared URL https://api.brazilmacro.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.brazilmacro.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 11 Sept 2026 | 27 Mar 2027 | RSA 2048 | SHA256-RSA | 25c6496783018741c5a413fefa93277 |
| SANs: api.brazilmacro.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.brazilmacro.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| brazilmacro.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.brazilmacro.com/mcp | Redirected | 307 | https://api.brazilmacro.com/mcp/ |
| streamable-http · followed | https://api.brazilmacro.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://api.brazilmacro.com/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
brazil_focus_revisions ~417
Detects whether Brazilian economists are revising inflation (IPCA), policy-rate (Selic), growth (PIB Total) or FX (Câmbio) expectations, and measures the speed and dispersion of those revisions — 1-week, 4-week and 13-week changes in the Focus survey median, plus a deterministic rising/falling/stable direction and accelerating/ decelerating/stable speed classification (method_id focus_revisions_v1). Built directly on Focus historical vintages — never recalculates a past date using data published after it. Use when: assessing sentiment shifts among professional economists for Brazil's main macro indicators, or whether a recent revision is speeding up or slowing down. Do not use when: you want market-implied pricing (use get_brazil_copom_path) or a market-vs-consensus comparison (use compare_brazil_market_vs_focus) — this tool is Focus-survey-only. Units are NOT always basis points — check the `unit` field in the response (bps for Selic/IPCA, percentage_points for PIB Total, BRL for Câmbio). Args: indicator: one of "Selic", "IPCA", "PIB Total", "Câmbio". reference_period: e.g. "2027" (the forecast year). Defaults to the current year. segment: "general" (all respondents) or "top5". Never mixed. as_of: optional YYYY-MM-DD date. Defaults to today. payment_token: required in staging ($0.05/call per pricing.yaml).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| as_of | – | – | – |
| discovery_source | – | – | – |
| indicator | string | yes | – |
| payment_token | – | – | – |
| reference_period | – | – | – |
| segment | string | – | – |
| session_id | – | – | – |
| synthetic_identity | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
brazil_inflation_breakeven ~346
Market-implied Brazilian inflation breakeven — Fisher's EXACT identity ((1+nominal)/(1+real) - 1), never the linear approximation — computed only where the nominal and real curves both have support at the same tenor (method_id breakeven_fisher_v1). Returns `nominal_zero_rate_pct` and `real_zero_rate_pct` alongside the breakeven so the result is auditable. IMPORTANT: this is NOT "expected inflation" — it embeds risk premium, liquidity and convexity effects. The response field is deliberately named `market_implied_inflation_breakeven`. Use when: assessing what the market is pricing for future inflation, as distinct from Focus survey expectations (use brazil_focus_revisions with indicator="IPCA" for that). Do not use when: you need either curve alone (use brazil_yield_curve / brazil_real_curve). Args: as_of: optional YYYY-MM-DD. Defaults to today. tenors: comma-separated subset of 1Y,2Y,3Y,5Y,7Y,10Y. Default: all. quote_side: "buy", "sell", or "mid" (default). payment_token: required in staging ($0.03/call per pricing.yaml).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| as_of | – | – | – |
| discovery_source | – | – | – |
| payment_token | – | – | – |
| quote_side | string | – | – |
| session_id | – | – | – |
| synthetic_identity | boolean | – | – |
| tenors | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
brazil_macro_actual ~355
Returns a Brazilian macro headline actual (IPCA, IPCA-15, GDP, PIM-PF industrial production, PMC retail sales, PMS services volume, or PNAD Contínua unemployment) with full release-vintage provenance — built on a release/vintage layer that NEVER overwrites an original published number when a later revision arrives (method_id macro_actual_v1). Use when: you need the current headline reading for a Brazilian macro indicator, or (via `vintage`) what was known at a specific historical instant vs. what is currently the revised/correct value. Do not use when: you want the surprise vs. consensus (use brazil_macro_surprise, IPCA only) or the release schedule (use brazil_macro_calendar). Args: indicator: one of IPCA, IPCA15, GDP, PIM_PF, PMC, PMS, PNAD_UNEMPLOYMENT. reference_period: e.g. "2026-07" (monthly) or "2026-Q2" (GDP). as_of: YYYY-MM-DD, REQUIRED when vintage="as_known". vintage: "latest" (currently-correct value, default), "first" (original release, revision_number=0), or "as_known" (what was known publicly at `as_of`).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| as_of | – | – | – |
| discovery_source | – | – | – |
| indicator | string | yes | – |
| payment_token | – | – | – |
| reference_period | string | yes | – |
| session_id | – | – | – |
| synthetic_identity | boolean | – | – |
| vintage | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
brazil_macro_calendar ~192
Official IBGE release calendar for Brazilian macro indicators (IPCA, IPCA-15, GDP, PIM-PF, PMC, PMS, PNAD Contínua unemployment), with status transitions scheduled -> released -> corrected. Use when: you need to know when the next release of a Brazilian macro indicator is scheduled, or whether a given period has been released yet. Args: event: optional filter to one indicator (e.g. "IPCA"). Omit for all. upcoming_only: if true (default), only events not yet released. limit: max events returned (default 20).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| discovery_source | – | – | – |
| event | – | – | – |
| limit | integer | – | – |
| payment_token | – | – | – |
| session_id | – | – | – |
| synthetic_identity | boolean | – | – |
| upcoming_only | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
brazil_macro_surprise ~234
Compare a Brazilian macroeconomic release with the latest public consensus that was available before the release, with full vintage and source provenance (method_id macro_surprise_v1). The consensus is ALWAYS the last Focus survey reading published strictly before the official release timestamp — never a reading published after it, and the actual is always the FIRST release, never a later revision. IMPORTANT: only computed for indicators with a methodologically valid, event-specific public consensus — currently IPCA only. GDP/PIM-PF/PMC/ PMS/PNAD_UNEMPLOYMENT raise an error rather than fabricate a consensus (use brazil_macro_actual for those — actual/momentum only, no surprise). Args: indicator: currently only "IPCA" is eligible. reference_period: e.g. "2026-07".
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| discovery_source | – | – | – |
| indicator | string | yes | – |
| payment_token | – | – | – |
| reference_period | string | yes | – |
| session_id | – | – | – |
| synthetic_identity | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
brazil_monetary_policy_divergence ~626
Assess divergence between Brazilian market-implied monetary policy, economist expectations, inflation breakevens and realized inflation surprises, using point-in-time public data with full provenance (method_id monetary_policy_divergence_v1). Consumes ONLY the already-homologated capability layer (market-vs-Focus meeting gaps, Focus Selic/IPCA 4-week revisions, the 5Y inflation breakeven and its 20-business-day change, and the latest eligible IPCA surprise) — never recomputes those engines and never fabricates a number a component doesn't support. Each of the 5 evidence components gets its own deterministic classification (strong_dovish..strong_ hawkish) with a versioned threshold set (threshold_version B4_THRESHOLDS_V1), quality-weighted by the underlying engine's own quality_status. `overall_signal` is a QUALITATIVE composite (strong_dovish/dovish/balanced/hawkish/strong_hawkish/ insufficient_evidence) — deliberately NOT a fabricated 0-100 score. `evidence_agreement` (0-1) tells you separately whether the components agree with each other, independent of the direction of the signal. IMPORTANT: `product_validation_status` is "internal_validated_external_ pending" until C0's external benchmark passes (see docs/C0_external_validation_protocol.md), then "validated" — several inputs (the market-implied Copom path, the real/breakeven curve) are themselves still individually pending external benchmark validation, never hidden here. This is macro intelligence, NOT an investment recommendation. Use when: assessing whether Brazilian market pricing, economist consensus, market-implied inflation and realized inflation data agree or diverge on the direction of monetary policy pressure. Do not use when: you need only one dimension — use compare_brazil_market_vs_focus, brazil_focus_revisions, brazil_inflation_breakeven, or brazil_macro_surprise directly. Ar…
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| as_of | – | – | – |
| discovery_source | – | – | – |
| horizon_meetings | integer | – | – |
| include_evidence | boolean | – | – |
| payment_token | – | – | – |
| session_id | – | – | – |
| synthetic_identity | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
brazil_real_curve ~336
Real (IPCA-linked) Brazilian sovereign zero-coupon curve, bootstrapped from Tesouro Direto NTN-B Principal (zero-coupon) and NTN-B (semi-annual real coupon) offered-security quotes. Built entirely from the bonds' own quoted real yields — no Focus/IPCA projection is used anywhere in this engine. curve_scope = "tesouro_direto_offered_securities" (see brazil_yield_curve). Note: Tesouro currently offers no short-dated real zero-coupon bond, so this curve typically has NO coverage for 1Y/2Y tenors — check `status` per tenor. Use when: you need Brazil's real (inflation-protected) rate curve. Do not use when: you need the nominal curve (brazil_yield_curve) or breakeven inflation (brazil_inflation_breakeven). Args: as_of: optional YYYY-MM-DD. Defaults to today. tenors: comma-separated subset of 1Y,2Y,3Y,5Y,7Y,10Y. Default: all. quote_side: "buy", "sell", or "mid" (default). payment_token: required in staging ($0.03/call per pricing.yaml).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| as_of | – | – | – |
| discovery_source | – | – | – |
| payment_token | – | – | – |
| quote_side | string | – | – |
| session_id | – | – | – |
| synthetic_identity | boolean | – | – |
| tenors | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
brazil_yield_curve ~333
Nominal Brazilian sovereign zero-coupon curve, bootstrapped from Tesouro Direto LTN (zero-coupon) and NTN-F (semi-annual coupon) offered-security quotes (method_id sovereign_zero_curve_bootstrap_v1). curve_scope = "tesouro_direto_offered_securities": this is NOT an institutional ANBIMA/Bloomberg ETTJ — it's derived from retail-offered public securities, published as open data (ODbL license). Tenors outside the curve's actual node coverage return status="unsupported", never extrapolated. Use when: you need Brazil's nominal risk-free curve shape or a specific nominal zero rate. Do not use when: you need the real (inflation-linked) curve (use brazil_real_curve) or breakeven inflation (use brazil_inflation_breakeven). Args: as_of: optional YYYY-MM-DD. Defaults to today. tenors: comma-separated subset of 1Y,2Y,3Y,5Y,7Y,10Y. Default: all. quote_side: "buy", "sell", or "mid" (default). payment_token: required in staging ($0.01/call per pricing.yaml).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| as_of | – | – | – |
| discovery_source | – | – | – |
| payment_token | – | – | – |
| quote_side | string | – | – |
| session_id | – | – | – |
| synthetic_identity | boolean | – | – |
| tenors | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
compare_brazil_market_vs_focus ~264
Compares the market-implied Copom path (DI1-derived) against the BCB Focus survey median, meeting-by-meeting (not just year-end), returning the gap in basis points per meeting and an overall dovish/hawkish classification (method_id market_vs_focus_meetings_v1). Use when: assessing whether Brazilian rates markets are pricing more or less monetary policy action than professional economists' consensus — useful for research agents, news agents, or risk agents monitoring Brazil-specific policy surprises. Do not use when: you only need one side of the comparison (use get_brazil_copom_path for market pricing alone, or Focus data directly for consensus alone). Args: as_of: optional YYYY-MM-DD date. Defaults to today. horizon: number of upcoming Copom meetings to compare (1-8, default 4). payment_token: required in staging ($0.15/call per pricing.yaml).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| as_of | – | – | – |
| discovery_source | – | – | – |
| horizon | integer | – | – |
| payment_token | – | – | – |
| session_id | – | – | – |
| synthetic_identity | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_brazil_copom_path ~344
Returns market-implied Brazilian Selic expectations for upcoming Copom meetings, derived from B3 DI1 futures via a meeting-step bootstrap (method_id copom_path_di1_v1). Each entry gives the implied Selic level and the implied change in basis points for that specific meeting date — not rounded to 25bp increments. Use when: estimating expected BCB policy changes, the terminal rate, or cumulative easing/tightening priced by the market over the next 1-8 Copom meetings. Do not use when: you want economists' survey expectations instead of market pricing (use brazil_focus_revisions) or a direct comparison between the two (use compare_brazil_market_vs_focus). Limitations: requires liquid DI1 data for the as_of date's most recent trading day; DU counts use the validated B3 trading calendar (A6.1). Args: as_of: optional YYYY-MM-DD date. Defaults to today. meetings: number of upcoming Copom meetings to return (1-8, default 4). agent_id, session_id, discovery_source: optional C1 telemetry fields. payment_token: required in staging for this priced capability ($0.10/call per pricing.yaml) — omit to get the simulated payment_required response instead of a result.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| as_of | – | – | – |
| discovery_source | – | – | – |
| meetings | integer | – | – |
| payment_token | – | – | – |
| session_id | – | – | – |
| synthetic_identity | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_brazil_selic_snapshot ~228
Returns Brazil's current policy rate (Selic target) plus realized short-term rates (Selic 252, CDI) and the last Copom decision. Use when: you need the current or historical Brazilian policy rate, or the most recent Copom decision, without needing forward-looking pricing. Do not use when: you need market expectations for FUTURE meetings — use get_brazil_copom_path or compare_brazil_market_vs_focus instead. Args: as_of: optional YYYY-MM-DD date for a historical snapshot (respects vintage — never uses data published after this date). Defaults to today. agent_id, session_id, discovery_source, payment_token: optional telemetry/access-policy fields (C1) — safe to omit; this capability is free and always returns 200 either way.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| as_of | – | – | – |
| discovery_source | – | – | – |
| payment_token | – | – | – |
| session_id | – | – | – |
| synthetic_identity | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the com.brazilmacro/brazil-macro-ai MCP server?
com.brazilmacro/brazil-macro-ai is an MCP server listed in the public MCP registry as com.brazilmacro/brazil-macro-ai. Brazil Macroeconomic and Financial Data AI Platform for AI agents. This page covers its hosted endpoint (https://api.brazilmacro.com/mcp).
Is the com.brazilmacro/brazil-macro-ai MCP server safe to use?
com.brazilmacro/brazil-macro-ai scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.brazilmacro/brazil-macro-ai MCP server expose?
com.brazilmacro/brazil-macro-ai exposes 11 tools: get_brazil_selic_snapshot, get_brazil_copom_path, compare_brazil_market_vs_focus, brazil_focus_revisions, brazil_yield_curve, and 6 more. Their descriptions and schemas cost roughly 3,675 tokens of context every time the server is loaded.
Does the com.brazilmacro/brazil-macro-ai MCP server require authentication?
No. We connected to com.brazilmacro/brazil-macro-ai without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.brazilmacro/brazil-macro-ai MCP server still maintained?
com.brazilmacro/brazil-macro-ai is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.