Privacy-preserving synthetic health data generation. FHIR R4/R5 compliant.
Privacy-preserving synthetic health data generation. FHIR R4/R5 compliant.
Is it safe?
No package registry to scan for CVEs.
No authentication — any process on your machine can connect to this server.
License not specified.
Last scanned 0 days ago.
Is it maintained?
Last commit 36 days ago.
Will it work with my client?
Transport: http. Remote server — may need mcp-remote proxy for some clients.
How much context will it use?
6 tools. Estimated ~800 tokens of your context window (0.4% of 200K).
What if it doesn't work?
Common issues: JSON syntax errors in config, network or firewall blocking. Setup guide covers troubleshooting.
{
"mcpServers": {
"k01": {
"url": "https://mcp.k01.is/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}No automated test available for this server. Check the GitHub README for setup instructions.
generate_synthetic_cohortGenerate synthetic patient cohorts with demographic and clinical constraints
search_patientsSearch a virtual patient database with advanced healthcare filters
get_patient_recordRetrieve a complete patient record with medication and condition summaries
get_patient_medicationsGet detailed medication records with ATC codes and therapeutic indications
get_patient_conditionsRetrieve patient conditions with ICD-10 codes and localized names
compare_fhir_versionsCompare the same patient data across FHIR R4 and R5
Last scanned 4h ago
No known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.