Sdmx Structure
NPM · @PIPEWORX/MCP-SDMX-STRUCTURE · 2 COMPONENTS
SDMX Structure MCP — dataflow dimensions and code lists for any SDMX 2.1 registry: Eurostat, OECD…
Available components
Last scanned (1 hour ago)
Scores higher than 72% of npm servers
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sdmx-structure). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 994 tokens (~331/item across 3 items; 3 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 +3
- Stability: unverified → 0.23 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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 6 Nov 2026 · Analysed npm/@pipeworx/mcp-sdmx-structure@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-sdmx-structure |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-sdmx-structure/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692339593 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a0d4aa41efff906a036e3d2219b3170dec9c2f079a1cf4e220f2acfd4997179cb4dc1d60aaf59a0258a6f7a5f164fac811aa2b300c7321278cc1c77db |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
sdmx_codelist ~298
Fetch one codelist's code->label mapping by id, from any SDMX 2.1 registry, without needing a dataflow. Use this when you already know a codelist id (e.g. from sdmx_dataflow_structure's `codelist` field, or from a dataset's documentation) and just need the codes. Example: sdmx_codelist({ registry: "ilo", id: "CL_ECO" }) or sdmx_codelist({ registry: "eurostat", id: "GEO", filter: "France" }).
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Override the registry's default maintaining agency id for this codelist, e.g. "SDMX" for a shared CL_FREQ. Most callers can omit this. |
| filter | string | – | Case-insensitive substring filter on code id or label, e.g. "france", "quarterly". |
| id | string | yes | Codelist id, e.g. "CL_ECO", "GEO", "CL_FREQ". |
| limit | number | – | Max codes to return (default 100, max 1000). |
| registry | string | yes | Which SDMX registry to query: eurostat, oecd, ecb, unsd, imf, bis, ilo, abs. |
| version | string | – | Codelist version. Defaults to "latest". |
No output schema declared.
No examples provided.
sdmx_dataflow_structure ~387
Get the structure of one dataflow from any SDMX 2.1 registry: its ordered dimensions and, for each, the valid codes with labels. This answers "what do the codes in dataflow X mean" and "what key do I need to pull data from it" — use it before calling a registry-specific get_data tool. Covers eurostat, oecd, ecb, unsd (UN Statistics Division via the data.un.org SDMX hub), imf, bis, ilo, abs. For ILO or ABS dataflows, prefer the ilostat/abs-au packs' own dataflow_structure tool — this one exists mainly for the other six. Example: sdmx_dataflow_structure({ registry: "eurostat", dataflow: "une_rt_m" }) or sdmx_dataflow_structure({ registry: "bis", dataflow: "WS_CBPOL" }).
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Override the registry's default maintaining agency id, e.g. "OECD.SDD.NAD" for an OECD dataflow published by a specific directorate. Most callers can omit this. |
| dataflow | string | yes | Dataflow id, e.g. "une_rt_m" (Eurostat), "WS_CBPOL" (BIS), "EER" (IMF). Case usually does not matter but pass it exactly as published. |
| max_codes_per_dimension | number | – | Cap codes returned per dimension (default 50, max 500). Codelists like country or region lists can have thousands of codes. |
| registry | string | yes | Which SDMX registry to query: eurostat, oecd, ecb, unsd, imf, bis, ilo, abs. |
| version | string | – | Dataflow version, e.g. "1.0". Defaults to "latest". |
No output schema declared.
No examples provided.
sdmx_find_dataflow ~251
Keyword-search a registry's full dataflow catalogue by id or name substring. Use this to find the dataflow id to pass to sdmx_dataflow_structure when you only know a topic. Example: sdmx_find_dataflow({ registry: "bis", query: "credit" }) or sdmx_find_dataflow({ registry: "oecd", query: "unemployment" }). For Eurostat specifically, the eurostat pack's own search_datasets tool searches its ~10,000-entry table of contents with richer metadata (last-update dates, time coverage) and is usually the better choice.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Restrict to one maintaining agency id instead of the registry default, e.g. "OECD.SDD.NAD". |
| limit | number | – | Max results to return (default 50, max 300). |
| query | string | yes | Case-insensitive substring to match against dataflow id or name, e.g. "unemployment", "credit", "exchange rate". |
| registry | string | yes | Which SDMX registry to query: eurostat, oecd, ecb, unsd, imf, bis, ilo, abs. |
No output schema declared.
No examples provided.
How do I install the Sdmx Structure MCP server?
Sdmx Structure runs locally as an npm package, launched with npx -y @pipeworx/mcp-sdmx-structure. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-sdmx-structure
claude mcp add pipeworx-io-sdmx-structure -- npx -y @pipeworx/mcp-sdmx-structure
What is the Sdmx Structure MCP server?
Sdmx Structure is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sdmx-structure. SDMX Structure MCP, dataflow dimensions and code lists for any SDMX 2.1 registry: Eurostat, OECD… This page covers its npm package (@pipeworx/mcp-sdmx-structure).
Is the Sdmx Structure MCP server safe to use?
Sdmx Structure scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Sdmx Structure MCP server expose?
Sdmx Structure exposes 3 tools: sdmx_dataflow_structure, sdmx_codelist, sdmx_find_dataflow. Their descriptions and schemas cost roughly 936 tokens of context every time the server is loaded.
Is the Sdmx Structure MCP server still maintained?
Sdmx Structure is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Sdmx Structure MCP server under?
Sdmx Structure declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Sdmx Structure MCP server?
VerifyMCP ran 16 checks on Sdmx Structure, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.