Types for IMF (International Monetary Fund) economic data
integration via the native TypeScript SDMX 3.0 REST client
(src/mcp/imf-mcp-client.ts), which calls
https://dataservices.imf.org/REST/SDMX_3.0/ directly.
Used to enrich EU Parliament articles with fresher macroeconomic context
than the World Bank WDI provides (IMF WEO ships 2025 actuals + 2026-2030
forecasts; WDI typically lags by 12+ months for the most recent vintage).
Wave 1 dual-source note
This module is additive. The World Bank types in ./world-bank.ts remain
the authoritative source for social/health/education/environment indicators
that IMF SDMX does not publish. IMF types cover the macro/fiscal/trade/
monetary subset plus native multi-year forecasts.
Transport history
The first Wave 1 iteration proxied through the Python
c-cf/imf-data-mcp MCP server. That transport was replaced with a
native TypeScript HTTP client so the stack remains npm-pure and
pinned per ISMS §7. The IMF_MCP_TOOLS identifier list is retained
as a stable "virtual tool" surface for the Stage-C editorial
fingerprint (see analysis/imf/indicator-catalog.md §6) and the
workflow probe. The earlier companion module src/utils/imf-data.ts
(parsers, indicator/country maps, HTML builders) was purged in the
April-2026 aggregator-pipeline migration.
Description
Types for IMF (International Monetary Fund) economic data integration via the native TypeScript SDMX 3.0 REST client (
src/mcp/imf-mcp-client.ts), which callshttps://dataservices.imf.org/REST/SDMX_3.0/directly.Used to enrich EU Parliament articles with fresher macroeconomic context than the World Bank WDI provides (IMF WEO ships 2025 actuals + 2026-2030 forecasts; WDI typically lags by 12+ months for the most recent vintage).
Wave 1 dual-source note
This module is additive. The World Bank types in
./world-bank.tsremain the authoritative source for social/health/education/environment indicators that IMF SDMX does not publish. IMF types cover the macro/fiscal/trade/ monetary subset plus native multi-year forecasts.Transport history
The first Wave 1 iteration proxied through the Python
c-cf/imf-data-mcpMCP server. That transport was replaced with a native TypeScript HTTP client so the stack remains npm-pure and pinned per ISMS §7. TheIMF_MCP_TOOLSidentifier list is retained as a stable "virtual tool" surface for the Stage-C editorial fingerprint (seeanalysis/imf/indicator-catalog.md §6) and the workflow probe. The earlier companion modulesrc/utils/imf-data.ts(parsers, indicator/country maps, HTML builders) was purged in the April-2026 aggregator-pipeline migration.See