Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Istat It

NPM · @PIPEWORX/MCP-ISTAT-IT · 2 COMPONENTS

ISTAT (Istituto Nazionale di Statistica) MCP — Italy's national statistics via the public SDMX 2.1…

+3 this week 83 Trust /100

Last scanned (9 hours ago)

Scores higher than 76% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

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-istat-it). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 584 tokens (~194/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 Management23
  • Stability observed for 7 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
What we tested

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 →

Changelog

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.

  • 5 Nov 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.

  • 3 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 1 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 80

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-istat-it@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-istat-it
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-istat-it/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637496166
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:c7ebcfb037af4590c0c627550c3d4dfc40c584b129e7c6054c8918fd32f4ae3e4d836154b558c03cf1a87bb84528859c6b50227050ac42b9672b19944

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~530 tokens

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 →

Tool Tokens
dataflow_structure ~114

Get the structure (Data Structure Definition) of one ISTAT dataset: its ordered dimensions and, for each, the valid codes. Use this to learn how to build the dot-separated SDMX key for get_data. The key positions correspond to the dimensions in order; an empty position is a wildcard. Example: dataflow_structure({ dataflow_id: "101_1015" }).

NameTypeReqDescription
dataflow_idstringyesISTAT dataflow id from list_dataflows, e.g. "101_1015".

No output schema declared.

No examples provided.

get_data ~274

Pull observations from an ISTAT dataset. `key` is a dot-separated SDMX dimension filter, one position per dimension in the order given by dataflow_structure; leave a position empty to wildcard it. Example: get_data({ dataflow_id: "101_1015", key: "A.IT...", start_period: "2021", end_period: "2023" }) selects annual (A), REF_AREA=IT (Italy), and wildcards the rest. Omit `key` (or pass "") to fetch all series — caution, this can be large. Returns decoded series with their dimension labels and per-period values.

NameTypeReqDescription
dataflow_idstringyesISTAT dataflow id, e.g. "101_1015".
end_periodstring–End period, e.g. "2023".
keystring–Dot-separated dimension filter (one position per dimension, empty = wildcard), e.g. "A.IT..." . Omit for all series.
last_nnumber–Return only the last N observations per series.
max_seriesnumber–Cap the number of decoded series returned (default 200).
start_periodstring–Start period, e.g. "2021", "2021-01", "2021-Q1".

No output schema declared.

No examples provided.

list_dataflows ~142

Browse or keyword-search ISTAT datasets (dataflows). Each result has an `id` (the dataflowId you pass to get_data / dataflow_structure) and an English name. ISTAT publishes ~4,800 datasets, so always pass `query` to filter unless you really want the whole list. Example: list_dataflows({ query: "unemployment" }) or list_dataflows({ query: "GDP" }).

NameTypeReqDescription
limitnumber–Max results to return (default 50).
querystring–Case-insensitive substring filter on dataset id or name, e.g. "population", "inflation", "GDP".

No output schema declared.

No examples provided.

Install

How do I install the Istat It MCP server?

Istat It runs locally as an npm package, launched with npx -y @pipeworx/mcp-istat-it. 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-istat-it

# add to Claude Code
claude mcp add pipeworx-io-istat-it -- npx -y @pipeworx/mcp-istat-it
Common questions

What is the Istat It MCP server?

Istat It is an MCP server listed in the public MCP registry as io.github.pipeworx-io/istat-it. ISTAT (Istituto Nazionale di Statistica) MCP, Italy's national statistics via the public SDMX 2.1… This page covers its npm package (@pipeworx/mcp-istat-it).

Is the Istat It MCP server safe to use?

Istat It scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Istat It MCP server expose?

Istat It exposes 3 tools: list_dataflows, dataflow_structure, get_data. Their descriptions and schemas cost roughly 530 tokens of context every time the server is loaded.

Is the Istat It MCP server still maintained?

Istat It is still listed as active in the MCP registry. We last reached this channel on 5 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 Istat It MCP server under?

Istat It 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 Istat It MCP server?

VerifyMCP ran 16 checks on Istat It, 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.