# Bioregistry (npm · @pipeworx/mcp-bioregistry)

Bioregistry MCP.

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

## Channel facts

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

Bioregistry runs locally as an npm package, launched with npx -y @pipeworx/mcp-bioregistry. 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-bioregistry -- npx -y @pipeworx/mcp-bioregistry
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-05 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 64, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.0 → 0.2.1

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

First indexed and scored.

## MCP tools (4)

### `prefix` (~67 tokens)

Fetch full Bioregistry metadata for a biological database prefix (e.g. "chebi", "hpo", "uniprot"), including canonical URI pattern, synonyms, homepage, and cross-registry mappings.

Input parameters:

- `prefix` (string, required): e.g. "chebi", "hpo"

### `search` (~58 tokens)

Search Bioregistry for biological database prefixes by substring match against prefix name, title, or description (e.g. "gene ontology"). Returns up to `limit` matching prefix records.

Input parameters:

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

### `resolve` (~37 tokens)

Resolve a CURIE (prefix:id) to a provider URL.

Input parameters:

- `curie` (string, required): e.g. "chebi:24867"

### `prefixes` (~55 tokens)

Paginate over all registered Bioregistry prefixes (2,000+); returns full prefix records for each entry. Use limit/offset to page through the complete registry.

Input parameters:

- `limit` (number)
- `offset` (number)

## Diagnostics

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

## Score history

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

## Common questions

### What is the Bioregistry MCP server?

Bioregistry is an MCP server listed in the public MCP registry as io.github.pipeworx-io/bioregistry. Bioregistry MCP. This page covers its npm package (@pipeworx/mcp-bioregistry).

### Is the Bioregistry MCP server safe to use?

Bioregistry scores 82 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 Bioregistry MCP server expose?

Bioregistry exposes 4 tools: prefix, search, resolve, prefixes. Their descriptions and schemas cost roughly 217 tokens of context every time the server is loaded.

### Is the Bioregistry MCP server still maintained?

Bioregistry 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 Bioregistry MCP server under?

Bioregistry 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 Bioregistry MCP server?

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