Skip to content
Back to the index

bioregistry

pipeworx.ioInfrastructure

PulseGate's liveness check found it on 24 Sep 2026; it has been in the index since 24 Sep 2026. How this is checked

Bioregistry MCP Server exposes Bioregistry data through a JSON-RPC MCP endpoint. It provides tools for prefix metadata lookup, substring search, CURIE resolution, and pagination across registered biological database prefixes for AI agents and bioinformatics workflows.

Inferred · not functionally tested

WebAPICloud-managed
bioregistry preview
Visit pipeworx.io

Overview

6 features

Purpose: Helping AI agents discover biological database metadata and resolve identifiers to provider URLs.

Inferred · not functionally tested

Audience: bioinformatics developers and AI agent builders

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

bioregistry sits in PulseGate's Frameworks & SDKs category. Inferred · not functionally tested: It focuses on helping AI agents discover biological database metadata and resolve identifiers to provider URLs. Inferred · not functionally tested: It is built as a B2B product for bioinformatics developers and AI agent builders. Basis unknown · not verified: bioregistry is available on the web and API.

Behind bioregistry is Pipeworx. Inferred · not functionally tested: Among its 6 catalogued features are prefix metadata lookup, prefix search, and CURIE resolution. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Prefix metadata lookup
  • Prefix search
  • CURIE resolution
  • Prefix pagination
  • JSON-RPC endpoint
  • MCP tools

Topics: Inferred · not functionally tested

Tags
bioregistrybioinformaticscurie-resolutionmcp-server

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCP
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed24 Sep · 22:19 UTC
    Bioregistry seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about bioregistry

What does bioregistry do?
Inferred · not functionally tested: Bioregistry focuses on helping AI agents discover biological database metadata and resolve identifiers to provider URLs. It is catalogued under Frameworks & SDKs on PulseGate.
Who is bioregistry for?
Inferred · not functionally tested: bioregistry is a B2B product built for bioinformatics developers and AI agent builders.
What platforms does bioregistry run on?
Basis unknown · not verified: bioregistry runs on the web and API.
Is bioregistry still active?
PulseGate's liveness check found it on 24 Sep 2026.
What are alternatives to bioregistry?
Similar projects tracked by PulseGate include biostudies, BioMCP, and biorxiv.biostudiesBioMCPbiorxiv
Who makes bioregistry?
bioregistry is developed by Pipeworx.
Does bioregistry have an API or integrations?
Inferred · not functionally tested: Yes — bioregistry exposes an MCP server.

Similar projects

Closest matches by what these projects do