MCP for AI agents
The MCP endpoint exposes the same read-only datasets as allowlisted tools; it cannot query people or execute writes.
POST /mcp
Public data infrastructure
Build with rare-disease community evidence
Search the canonical catalogue and consume privacy-preserving community, treatment, symptom and quality-of-life aggregates through stable read-only interfaces.
REST API v1
All endpoints are read-only, accept locale as a query parameter and return explicit methodology, provenance or licence notices.
| Dataset | Endpoint | Publication rule |
|---|---|---|
| Disease search | GET /api/v1/diseases?q={query} | Canonical terms and reviewed legacy communities |
| Disease catalogue | GET /api/v1/diseases/{slug} | No personal data |
| Community maturity | GET /api/v1/diseases/{slug}/community | Aggregate counts only |
| Reported treatments | GET /api/v1/diseases/{slug}/treatments | At least 3 independent reports |
| Quality of life | GET /api/v1/diseases/{slug}/quality-of-life | Cohorts of at least 10 observations |
| Reported symptoms | GET /api/v1/diseases/{slug}/symptoms | Cells of at least 5 respondents |
Example
curl --get 'https://diseasemaps.org/api/v1/diseases/celiac/quality-of-life' \
--data-urlencode 'locale=cs'Successful aggregate responses include cache validators. Use ETag and If-None-Match to avoid downloading unchanged data.
Traceable by design
Catalogue releases retain source, version, checksum and licence metadata. Community datasets describe their method and update date.
Privacy thresholds
The service suppresses small cells and never returns emails, coordinates, user identifiers, source answers or clinical microdata.