# Oneinfo Storage (npm · @pipeworx/mcp-oneinfo-storage) Italian regulated disclosures direct from 1INFO — keyless, same-day-fresh. - Trust score: 80/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-oneinfo-storage/oneinfo-storage-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-oneinfo-storage/oneinfo-storage-mcp) - npm · `@pipeworx/mcp-oneinfo-storage`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-oneinfo-storage/pipeworx-mcp-oneinfo-storage.md), [page](https://verifymcp.io/servers/pipeworx-io-oneinfo-storage/pipeworx-mcp-oneinfo-storage) ## Channel facts - Registry: `npm` - Package: `@pipeworx/mcp-oneinfo-storage` - Version: `0.2.1` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 100/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - No production dependencies, so there is no dependency health to assess. - **Provenance & Transparency**: 97/100 - Source repository is publicly reachable at the declared URL. - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-oneinfo-storage). - Clear OSI-approved license (MIT). - Actively maintained (last published 1 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 52/100 - AI-judged instruction clarity (good). - 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. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 23/100 - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### 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. ### Claude ```bash claude mcp add pipeworx-io-oneinfo-storage -- npx -y @pipeworx/mcp-oneinfo-storage ``` ### Cursor ```json { "mcpServers": { "pipeworx-io-oneinfo-storage": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-oneinfo-storage" ] } } } ``` ### VS Code ```json { "servers": { "pipeworx-io-oneinfo-storage": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-oneinfo-storage" ] } } } ``` ### Codex ```bash codex mcp add pipeworx-io-oneinfo-storage -- npx -y @pipeworx/mcp-oneinfo-storage ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "pipeworx-io-oneinfo-storage": { "type": "local", "command": [ "npx", "-y", "@pipeworx/mcp-oneinfo-storage" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add pipeworx-io-oneinfo-storage --command npx --arg -y --arg @pipeworx/mcp-oneinfo-storage ``` ### Hermes ```yaml mcp_servers: pipeworx-io-oneinfo-storage: command: "npx" args: ["-y", "@pipeworx/mcp-oneinfo-storage"] ``` ### Netclaw ```json { "McpServers": { "pipeworx-io-oneinfo-storage": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "@pipeworx/mcp-oneinfo-storage" ] } } } ``` ### Vellum ```bash assistant mcp add pipeworx-io-oneinfo-storage -t stdio -c npx -a -y @pipeworx/mcp-oneinfo-storage ``` ### Other ```json { "mcpServers": { "pipeworx-io-oneinfo-storage": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-oneinfo-storage" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 80, +16) - [security improvement] Malware scan: unverified → pass ### 2026-11-03 (score 64, −15) - [security regression] Malware scan: pass → unverified - [functional] Package version: 0.2.0 → 0.2.1 ### 2026-11-02 (score 79, +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. ### 2026-10-31 (score 78, +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. ### 2026-10-30 (score 77, 0) - [functional regression] Security disclosure: unverified → fail ### 2026-10-29 (score 77) First indexed and scored. ## MCP tools (2) ### `oneinfo_search_disclosures` (~1110 tokens) 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.… Input parameters: - `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. ### `oneinfo_get_disclosure` (~170 tokens) 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). Input parameters: - `date` (string, required): The disclosure's publication date (YYYY-MM-DD, Europe/Rome), from the same search result (published_at_local's date part). - `id` (string, required): 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). ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-oneinfo-storage/pipeworx-mcp-oneinfo-storage#diagnostics ## Score history - 2026-11-05: 80 - 2026-11-04: 80 - 2026-11-03: 64 - 2026-11-02: 79 - 2026-11-01: 78 - 2026-10-31: 78 - 2026-10-30: 77 - 2026-10-29: 77 ## Common questions ### 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. ### What did VerifyMCP test on the Oneinfo Storage MCP server? VerifyMCP ran 16 checks on Oneinfo Storage, 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. ## Links - npm package: https://www.npmjs.com/package/@pipeworx/mcp-oneinfo-storage - Socket report: https://socket.dev/npm/package/@pipeworx/mcp-oneinfo-storage - Repository: https://github.com/pipeworx-io/mcp-oneinfo-storage - Website: https://pipeworx.io/packs/oneinfo-storage - Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-oneinfo-storage/pipeworx-mcp-oneinfo-storage.xml - Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-oneinfo-storage/pipeworx-mcp-oneinfo-storage/changelog.json - Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-oneinfo-storage/pipeworx-mcp-oneinfo-storage.json - HTML version of this page: https://verifymcp.io/servers/pipeworx-io-oneinfo-storage/pipeworx-mcp-oneinfo-storage