MCP server for the National Bank of Belgium SDMX statistical API (221 dataflows).
MCP server for the National Bank of Belgium SDMX statistical API. Exposes the 221 NBB dataflows (194 BE2 + 27 IMF/SDDS) as 6 LLM-friendly tools and 3 browsable resources, with a bundled enriched catalogue so the LLM can discover, describe, and query dataflows without redundant API Upstream: (NSI Web Service v8) Transport: stdio (standard MCP) Platforms: Linux, macOS, Windows 221 dataflows…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
MCP server for the National Bank of Belgium SDMX statistical API. Exposes the 221 NBB dataflows (194 BE2 + 27 IMF/SDDS) as 6 LLM-friendly tools and 3 browsable resources, with a bundled enriched catalogue so the LLM can discover, describe, and query dataflows without redundant API Upstream: (NSI Web Service v8) Transport: stdio (standard MCP) Platforms: Linux, macOS, Windows 221 dataflows classified into 14 categories — see DATAFLOWSCATALOG.md The package ships with the full enriched catalogue…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.