Oneinfo Storage
NPM · @PIPEWORX/MCP-ONEINFO-STORAGE · 2 COMPONENTS
Italian regulated disclosures direct from 1INFO — keyless, same-day-fresh.
Available components
Last scanned (14 hours ago)
Scores higher than 65% of npm servers
Category Finance and Payments
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-oneinfo-storage). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1334 tokens (~667/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 77
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-oneinfo-storage@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-oneinfo-storage |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-oneinfo-storage/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3679710321 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:dd5e57fb88b6e5eb138f5a812b84b98d3c2b8310f49f30a1245da8f5960c682bff69c540892f96eda6311165b61840eef9e0a606b490d7b9a2d985e43 |
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 →
oneinfo_get_disclosure ~170
Fetch a single 1INFO disclosure by its protocolCode id and publication date, as returned by oneinfo_search_disclosures. This source has no by-id-only lookup endpoint, only by-day listings, so both id and date are required. Returns the shaped record — company, title, category, timestamp, and the document URL (with the .pdf-suffix / fiscal-year gotchas already handled).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | The disclosure's publication date (YYYY-MM-DD, Europe/Rome), from the same search result (published_at_local's date part). |
| id | string | yes | protocolCode, e.g. "171904_oneinfo", from an oneinfo_search_disclosures result (its bare id, without any .pdf/.zip suffix — this tool adds the right one). |
No output schema declared.
No examples provided.
oneinfo_search_disclosures ~1,110
Search Italian regulated company disclosures from 1INFO, one of Italy's two EU Transparency Directive Officially Appointed Mechanisms (the other is eMarket Storage — use emarket-storage's emarket_search_disclosures for issuers covered there instead, e.g. WEBUILD/SAIPEM). Identify the issuer with company (free-text name, resolved against 1INFO's own 314-issuer list) or ndg (1INFO's internal numeric issuer id, from a prior result) — there is no ISIN field on this source, and LEI only appears embedded in the filename of XBRL-tagged annual-report ZIPs (see the returned document_url for those). BOTH ARE OPTIONAL — omit company/ndg entirely to get every 1INFO issuer's disclosures in the date window in ONE call (the client-side scan then has no ndg to filter on, so every scanned row is a match); cheaper than one call per issuer for a multi-issuer daily check. date_to IS INCLUSIVE (the last local-calendar day you want, Europe/Rome). COVERAGE: 1INFO issuers only — a second Italian mechanism, eMarket Storage, covers a separate set (e.g. WEBUILD) and is not included; an unmatched company name is reported as "not a 1INFO issuer", not as an error. NO SERVER-SIDE ISSUER FILTER exists on this source, so a company/ndg search scans recent storage-date-ordered pages client-side up to a bounded depth — the response's scanned.oldest_date_local says honestly how far back it looked; a rarely-filing issuer may need a narrower/older date_from to surface. fiscal_year is read from the document's own title when it is not an XBRL package (fiscal_year_source tells you which rule produced it — "xbrl_metadata", "title", or "deposit_date_fallback" when the title had no usable year); it is NOT simply the deposit year. Category codes: 1.1=1.1 Relazione finanziaria annuale e relazione di revisione annuale; 1.2=1.2 Relazioni finanziarie semestrali e relazioni di revisione semestrali/revisioni limitate; 1.3=1.3 Pagamento ai governi; 2.1=2.1 Stato membro d'origine; 2.2=2.2 Informazioni privilegiate; 2.…
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category code to filter by, e.g. "2.2" for Informazioni privilegiate. This is the one filter 1INFO's own API honors server-side. See the tool description for the full code list. A row can carry more… |
| company | string | – | Free-text issuer name, e.g. "SOMEC", "IREN". Resolved against 1INFO's own 314-issuer picklist (name match, not a fulltext search). If it matches more than one issuer equally well, the response lists… |
| date_from | string | – | Only disclosures published on or after this date (YYYY-MM-DD, Europe/Rome calendar date, inclusive). If date_to is omitted, this tool searches just this one day. |
| date_to | string | – | Only disclosures published on or before this date (YYYY-MM-DD, Europe/Rome calendar date, INCLUSIVE — the last day you want included). |
| limit | number|string | – | Number of disclosures to return (1-50). Default 10. |
| ndg | string|number | – | 1INFO's internal issuer id, e.g. "484" (IREN). Use the value returned by a previous company search to skip name resolution. |
| offset | number|string | – | Result offset for pagination within the already-scanned match set. Default 0. |
No output schema declared.
No examples provided.
How do I install the Oneinfo Storage MCP server?
Oneinfo Storage runs locally as an npm package, launched with npx -y @pipeworx/mcp-oneinfo-storage. 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-oneinfo-storage
claude mcp add pipeworx-io-oneinfo-storage -- npx -y @pipeworx/mcp-oneinfo-storage
What is the Oneinfo Storage MCP server?
Oneinfo Storage is an MCP server listed in the public MCP registry as io.github.pipeworx-io/oneinfo-storage. Italian regulated disclosures direct from 1INFO, keyless, same-day-fresh. This page covers its npm package (@pipeworx/mcp-oneinfo-storage).
Is the Oneinfo Storage MCP server safe to use?
Oneinfo Storage scores 80 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 Oneinfo Storage MCP server expose?
Oneinfo Storage exposes 2 tools: oneinfo_search_disclosures, oneinfo_get_disclosure. Their descriptions and schemas cost roughly 1,280 tokens of context every time the server is loaded.
Is the Oneinfo Storage MCP server still maintained?
Oneinfo Storage 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 Oneinfo Storage MCP server under?
Oneinfo Storage declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.