# Hpo Api (npm · @pipeworx/mcp-hpo-api)

HPO API MCP.

- Trust score: 81/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`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-hpo-api/hpo-api-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-hpo-api/hpo-api-mcp)
- npm · `@pipeworx/mcp-hpo-api`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-hpo-api/pipeworx-mcp-hpo-api.md), [page](https://verifymcp.io/servers/pipeworx-io-hpo-api/pipeworx-mcp-hpo-api)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-hpo-api`
- 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-hpo-api).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 673 tokens (~96/item across 7 items; 7 tools + 0 resources), lean.
  - 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**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 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.

### Claude

```bash
claude mcp add pipeworx-io-hpo-api -- npx -y @pipeworx/mcp-hpo-api
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-hpo-api": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-hpo-api"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-hpo-api": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-hpo-api"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-hpo-api -- npx -y @pipeworx/mcp-hpo-api
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-hpo-api": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-hpo-api"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-hpo-api --command npx --arg -y --arg @pipeworx/mcp-hpo-api
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-hpo-api:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-hpo-api"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-hpo-api": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-hpo-api"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-hpo-api -t stdio -c npx -a -y @pipeworx/mcp-hpo-api
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-hpo-api": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-hpo-api"
      ]
    }
  }
}
```

## 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-03 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 65, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 80, +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.

### 2026-10-30 (score 79, +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.

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (7)

### `term` (~91 tokens)

"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).

Input parameters:

- `id` (string, required)

### `search` (~117 tokens)

"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.

Input parameters:

- `limit` (number)
- `page` (number)
- `query` (string, required)

### `term_children` (~82 tokens)

"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).

Input parameters:

- `id` (string, required)

### `term_parents` (~61 tokens)

"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.

Input parameters:

- `id` (string, required)

### `term_descendants` (~74 tokens)

"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).

Input parameters:

- `id` (string, required)

### `gene_diseases` (~96 tokens)

"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).

Input parameters:

- `id` (string, required)

### `disease_phenotypes` (~98 tokens)

"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).

Input parameters:

- `id` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-hpo-api/pipeworx-mcp-hpo-api#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 65
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

## Common questions

### 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.

### What did VerifyMCP test on the Hpo Api MCP server?

VerifyMCP ran 16 checks on Hpo Api, 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-hpo-api
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-hpo-api
- Repository: https://github.com/pipeworx-io/mcp-hpo-api
- Website: https://pipeworx.io/packs/hpo-api
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-hpo-api/pipeworx-mcp-hpo-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-hpo-api/pipeworx-mcp-hpo-api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-hpo-api/pipeworx-mcp-hpo-api.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-hpo-api/pipeworx-mcp-hpo-api