Privacy-preserving synthetic health data generation. FHIR R4/R5 compliant.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"k01": {
"url": "https://mcp.k01.is/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Generate and query clinically realistic synthetic health data directly from your AI workflow.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in health / data
Manage Supabase projects — databases, auth, storage, and edge functions
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.
MCP Security Weekly
Get CVE alerts and security updates for Synthetic Health Data MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Generate and query clinically realistic synthetic health data directly from your AI workflow.
K01's MCP server gives AI agents and LLM-powered tools access to privacy-preserving synthetic health data generation. Generate FHIR-compliant patient cohorts, query structured EHR data, and compare across FHIR versions — all with built-in differential privacy. No real patient data is involved at any point.
This repository contains documentation and configuration for the K01 MCP server. The server implementation is proprietary and runs on K01 infrastructure.
| Tool | Description | Key Parameters |
|---|---|---|
generate_synthetic_cohort | Generate synthetic patient cohorts with demographic and clinical constraints | count, age_min/age_max, gender, condition (ICD-10), seed, locale |
search_patients | Search a virtual patient database with advanced healthcare filters | gender, birthdate, numberOfMedicinesFrom/To, conditionTypes, locale |
get_patient_record | Retrieve a complete patient record with medication and condition summaries | patient_id, fhir_version |
get_patient_medications | Get detailed medication records with ATC codes and therapeutic indications | patient_id, seed, fhir_version |
get_patient_conditions | Retrieve patient conditions with ICD-10 codes and localized names | patient_id, seed, fhir_version |
compare_fhir_versions | Compare the same patient data across FHIR R4 and R5 | patient_id, resource_type |
All tools support both FHIR R4 and R5. See docs/tools.md for full parameter documentation.
Add to your Claude Desktop configuration (Settings > MCP Servers):
{
"mcpServers": {
"k01": {
"url": "https://mcp.k01.is/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Add to your Cursor MCP configuration (.cursor/mcp.json):
{
"mcpServers": {
"k01": {
"url": "https://mcp.k01.is/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Restart the application after adding the configuration. The K01 tools will appear in the tool list.
The K01 MCP server uses Bearer token authentication. Include your API key in the Authorization header.
To get an API key, contact K01 at k01.is. Self-service key provisioning is coming soon.
See docs/authentication.md for details.
"Generate 100 patients aged 40-65 with Type 2 diabetes"
The generate_synthetic_cohort tool creates a FHIR Bundle with Patient, Condition, MedicationStatement, Procedure, and Observation resources:
generate_synthetic_cohort(count=100, age_min=40, age_max=65, condition="E11.9", seed=42)
"Find patients with 3+ medications and chronic conditions"
search_patients(numberOfMedicinesFrom=3, conditionTypes="chronic", _count=20)
"How do this patient's medications look in R4 vs R5?"
compare_fhir_versions(patient_id="0101302989", resource_type="Medication")
See docs/examples.md for more workflows.
All data generated by K01 is fully synthetic. No real patient data is used, stored, or referenced at any point in the pipeline.