Mondo
NPM · @PIPEWORX/MCP-MONDO · 2 COMPONENTS
Mondo — condition-string resolver onto the Mondo Disease Ontology.
Available components
Last scanned (3 hours ago)
Scores higher than 68% of npm servers
Category Health and Science
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-mondo). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 415 tokens (~415/item across 1 items; 1 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-mondo@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-mondo |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-mondo/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655539368 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3a666c35aaf54a81022c86b66a33fcd8a0325330ab9b79f9b41e5928a86df725ba5224e0d638e9e9e3eba4353df0a6ce779bd6d47e67900a5460f2184 |
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 →
mondo_resolve_condition ~364
Resolve free-text condition/disease strings — e.g. a clinical trial registry's "conditions" field ("Carcinoma, Non-Small-Cell Lung"), or a drug label's Indications and Usage wording — onto the Mondo Disease Ontology (MONDO), via EBI OLS4 full-text search plus MyDisease.info cross-references. Accepts a batch (1-25) of condition strings. For each, returns the original wording verbatim, the best MONDO id + label, and a match_quality you can trust: "exact-label" (identical to the Mondo term's primary label), "exact-synonym" (identical to a listed exact synonym), "broader"/"narrower" (the string exactly names a parent or child term reached via the Mondo hierarchy, not the top full-text hit itself), or "fuzzy" (closest full-text match, not a confirmed exact term — treat with caution). Also carries xrefs (OMIM, Orphanet, DOID, UMLS, MeSH) for the matched id. A string with no plausible Mondo term returns match_quality "no-match" with the queries tried and the nearest candidates found, never a bare empty result. Set expand:true to also get the resolved term's descendant MONDO ids, for building a subtype-inclusive filter (e.g. "any subtype of non-small cell lung carcinoma").
| Name | Type | Req | Description |
|---|---|---|---|
| conditions | array | yes | 1-25 free-text condition/disease strings, e.g. ["Non-small Cell Lung Cancer", "type 2 diabetes mellitus"]. |
| expand | boolean | – | When true, also return the resolved term's descendant MONDO ids (all subtypes) for each result. Default false. |
No output schema declared.
No examples provided.
How do I install the Mondo MCP server?
Mondo runs locally as an npm package, launched with npx -y @pipeworx/mcp-mondo. 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-mondo
claude mcp add pipeworx-io-mondo -- npx -y @pipeworx/mcp-mondo
What is the Mondo MCP server?
Mondo is an MCP server listed in the public MCP registry as io.github.pipeworx-io/mondo. Mondo, condition-string resolver onto the Mondo Disease Ontology. This page covers its npm package (@pipeworx/mcp-mondo).
Is the Mondo MCP server safe to use?
Mondo scores 81 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 Mondo MCP server expose?
Mondo exposes 1 tool: mondo_resolve_condition. Their descriptions and schemas cost roughly 364 tokens of context every time the server is loaded.
Is the Mondo MCP server still maintained?
Mondo 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 Mondo MCP server under?
Mondo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.