Hpo Api
NPM · @PIPEWORX/MCP-HPO-API · 2 COMPONENTS
HPO API MCP.
Available components
Last scanned (6 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-hpo-api). 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 673 tokens (~96/item across 7 items; 7 tools + 0 resources), lean.Pass
- 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 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-hpo-api@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-hpo-api |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-hpo-api/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637393849 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d7d403b798437bfaa3def76c333f0601d1597a39dbd6de28d661cec58760706b9272cd10ffb5c50be35cff70d72825b78d8f86085741956a0f2fb4aa6 |
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 →
disease_phenotypes ~98
"What symptoms / clinical features does [disease] cause" / "HPO phenotypes for [OMIM N]" / "clinical signs of [rare disease]" — list HPO phenotype terms for a disease ID (OMIM:N, ORPHA:N, or MONDO:N format). Use to enumerate clinical features of rare diseases. Example ID: OMIM:154700 (Marfan syndrome).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
gene_diseases ~96
"What diseases is gene [NCBIGene:N] associated with" / "diseases linked to gene [X]" / "TP53 disease associations" — fetch diseases associated with a gene ID (NCBIGene:N format). Use for gene-to-disease lookups in rare-disease research, variant prioritization. Example ID: NCBIGene:7157 (TP53).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
search ~117
"HPO term for [symptom]" / "phenotype code for [clinical sign]" / "find HPO IDs about [feature]" / "what's the HPO for seizures / autism / short stature" — text search the Human Phenotype Ontology (HPO). Returns ranked terms with HP: IDs. Use to map clinical descriptions to standard ontology terms for rare-disease workups, genomics, or clinical phenotype databases.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| page | number | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
term ~91
"What does HP:[N] mean" / "look up HPO phenotype [ID]" — fetch a single Human Phenotype Ontology (HPO) term by ID. HPO is the standard ontology for clinical phenotypes used in rare-disease research. Returns label, definition, synonyms, cross-references. Example ID: HP:0001250 (Seizure).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
term_children ~82
"More specific HPO phenotypes under [HP:N]" / "child terms of [phenotype]" — direct children of an HPO term in the ontology graph. Use to narrow from a general phenotype (e.g. "Abnormality of the nervous system") to specifics (seizures, ataxia, etc).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
term_descendants ~74
"All phenotypes under [HP:N]" / "full subtree of [HPO term]" — transitive descendants (children, grandchildren, …) of an HPO term. Use for exhaustive coverage (e.g. "every cardiac phenotype" via descendants of HP:0001626).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
term_parents ~61
"What broader phenotype is [HP:N] under" / "parent term of [HPO ID]" — direct parents of an HPO term in the ontology graph. Use to walk up to a more general phenotype class.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Hpo Api MCP server?
Hpo Api runs locally as an npm package, launched with npx -y @pipeworx/mcp-hpo-api. 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-hpo-api
claude mcp add pipeworx-io-hpo-api -- npx -y @pipeworx/mcp-hpo-api
What is the Hpo Api MCP server?
Hpo Api is an MCP server listed in the public MCP registry as io.github.pipeworx-io/hpo-api. HPO API MCP. This page covers its npm package (@pipeworx/mcp-hpo-api).
Is the Hpo Api MCP server safe to use?
Hpo Api 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 Hpo Api MCP server expose?
Hpo Api exposes 7 tools: term, search, term_children, term_parents, term_descendants, and 2 more. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Is the Hpo Api MCP server still maintained?
Hpo Api 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 Hpo Api MCP server under?
Hpo Api declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.