@pipeworx/bioregistry
Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/bioregistry’s. Install: one-click buttons
Connect to just the @pipeworx/bioregistry pack
https://gateway.pipeworx.io/bioregistry/mcp — only @pipeworx/bioregistry’s own tools, nothing else in the catalog.
No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.
Tools: 4
Bioregistry MCP — meta-registry of biomedical identifier prefixes (~1500 prefixes from UniProt, ChEBI, HPO, MONDO, RxNorm, etc.). Keyless.
Tools
prefix(prefix)— prefix metadata (URL templates, providers, license)search(query, limit?)— substring search over prefixesresolve(curie)— resolve a CURIE (e.g.chebi:24867) to a provider URLprefixes(limit?, offset?)— paginate over all prefixes
Data source
https://bioregistry.io/api/
Tools
- prefix — Fetch full Bioregistry metadata for a biological database prefix (e.g. “chebi”, “hpo”, “uniprot”), including canonical URI pattern, synonyms, homepage, and cross-registry mappings.
- search — Search Bioregistry for biological database prefixes by substring match against prefix name, title, or description (e.g. “gene ontology”). Returns up to
limitmatching prefix records. - resolve — Resolve a CURIE (prefix:id) to a provider URL.
- prefixes — Paginate over all registered Bioregistry prefixes (2,000+); returns full prefix records for each entry. Use limit/offset to page through the complete registry.
Tools
prefix— Fetch full Bioregistry metadata for a biological database prefix (e.g. chebi , hpo , uniprot ), including canonical URI pattern, synonyms, homepage, and cross-registry mappings.prefixes— Paginate over all registered Bioregistry prefixes (2,000+); returns full prefix records for each entry. Use limit/offset to page through the complete registry.resolve— Resolve a CURIE (prefix:id) to a provider URL.search— 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.