Iso
NPM · @PIPEWORX/MCP-ISO · 2 COMPONENTS
ISO Standards MCP.
Available components
Last scanned (3 hours ago)
Scores higher than 81% of npm servers
Category Education and Research
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-iso). 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 Usability76
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 520 tokens (~130/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 81
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-iso@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-iso |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-iso/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637493827 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:633b7cc9c78d65c632802a045c95eb26674200a6ded37b472e3a63654182ecf951939983b2fcf8c40d1973927d47013e3acd70b0167dbfb4f8a9f430b |
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 →
compliance_catalog ~79
Curated catalogue of the compliance-relevant ISO standards (ISMS/27000, privacy, AI/42000, quality, continuity, risk) → ISO number, family and summary. Static name→number resolver; pass a number to get_standard for the live record.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional filter on number/name/summary/family. |
No output schema declared.
No examples provided.
get_standard ~142
Full record for one ISO standard by number ("27001") or reference ("ISO/IEC 27001:2022"): title, abstract, status, edition, publication date, ICS, committee, the supersession chain, the correct iso.org page, and a best-effort live price. The reliable lookup (resolves any standard via its catalogue id).
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | – | ISO number or reference, any form: "27001", "ISO 9001", "ISO-9001", "ISO9001", "ISO/IEC 42001", "ISO 9001:2015". (The `reference` arg is also accepted.) |
No output schema declared.
No examples provided.
open_data_files ~55
URLs for the ISO Open Data bulk files (deliverables metadata, ICS classification, technical committees), ODC-By 1.0. The deliverables file is what backs this pack. Use to ingest the full dataset yourself.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_standards ~193
Search the full ISO catalogue (~all deliverables) by keyword across reference, title and abstract, with optional filters. Returns reference, title, status, abstract snippet, committee and the iso.org link. Use to find standards on a topic ("supply chain security", "medical device risk").
| Name | Type | Req | Description |
|---|---|---|---|
| committee | string | – | Filter by owner committee, e.g. "JTC 1/SC 27" (substring). |
| ics | string | – | Filter by ICS classification code prefix, e.g. "35.030" (IT security). |
| limit | number | – | Max results (default 20, max 50). |
| query | string | yes | Keywords matched against title + abstract + reference (full-text). |
| status | string | – | Filter by publication status (prefix match). |
| type | string | – | Filter by deliverable type: IS, TR, TS, PAS, Guide, … |
No output schema declared.
No examples provided.
How do I install the Iso MCP server?
Iso runs locally as an npm package, launched with npx -y @pipeworx/mcp-iso. 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-iso
claude mcp add pipeworx-io-iso -- npx -y @pipeworx/mcp-iso
What is the Iso MCP server?
Iso is an MCP server listed in the public MCP registry as io.github.pipeworx-io/iso. ISO Standards MCP. This page covers its npm package (@pipeworx/mcp-iso).
Is the Iso MCP server safe to use?
Iso scores 84 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 Iso MCP server expose?
Iso exposes 4 tools: search_standards, get_standard, compliance_catalog, open_data_files. Their descriptions and schemas cost roughly 469 tokens of context every time the server is loaded.
Is the Iso MCP server still maintained?
Iso 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 Iso MCP server under?
Iso declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.