Skip to content
Back to the index

mydisease

pipeworx.ioMedical & telehealth

No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked

Mydisease is an MCP and JSON-RPC API for searching diseases and retrieving aggregated records by ontology identifier. It combines disease ontology, gene-disease, phenotype, and chemical-disease annotations for biomedical researchers and software developers.

Inferred · not functionally tested

WebAPICloud-managed
mydisease preview
Visit pipeworx.io

Overview

6 features

Purpose: Finding canonical disease identifiers and consolidated biomedical annotations across multiple disease databases.

Inferred · not functionally tested

Audience: biomedical researchers and developers

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.

mydisease sits in PulseGate's Medical & telehealth category. Inferred · not functionally tested: It focuses on finding canonical disease identifiers and consolidated biomedical annotations across multiple disease databases. Inferred · not functionally tested: mydisease is a B2B product aimed at biomedical researchers and developers. Basis unknown · not verified: It ships for the web and API.

Behind mydisease is Pipeworx. Inferred · not functionally tested: Key capabilities include disease search, ontology lookup, and disease annotations. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

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

Tasks: Inferred · not functionally tested

  • Disease search
  • Ontology lookup
  • Disease annotations
  • Gene associations
  • Phenotype data
  • Chemical relationships

Topics: Inferred · not functionally tested

Tags
disease-searchbiomedical-annotationsontology-lookupmcp-server

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCPAPI
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. Indexed10 Oct · 00:02 UTC
    Mydisease seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about mydisease

What does mydisease do?
Inferred · not functionally tested: Mydisease focuses on finding canonical disease identifiers and consolidated biomedical annotations across multiple disease databases. It is catalogued under Medical & telehealth on PulseGate.
Who should use mydisease?
Inferred · not functionally tested: mydisease is a B2B product built for biomedical researchers and developers.
What platforms does mydisease run on?
Basis unknown · not verified: mydisease runs on the web and API.
Is mydisease still active?
Unverified. mydisease has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What are alternatives to mydisease?
Similar projects tracked by PulseGate include disease, myhealthfinder, and mondo.diseasemyhealthfindermondo
Who makes mydisease?
mydisease is developed by Pipeworx.
Does mydisease have an API or integrations?
Inferred · not functionally tested: Yes — mydisease exposes an MCP server and a public API.

Similar projects

Closest matches by what these projects do