glama/nslc7779/korea-health-mcp-server/kohealth_get_disease_stats / alternatives

Live alternatives to glama/nslc7779/korea-health-mcp-server/kohealth_get_disease_stats

The best live alternatives to glama/nslc7779/korea-health-mcp-server/kohealth_get_disease_stats right now are mcp-registry/io.github.rarasai/raras/get_disease, mcp-registry/io.github.rarasai/raras/get_disease_sus_coverage, mcp-registry/io.github.andrew-sondgeroth/zipexplore-mcp/get_healthcare_profile, mcp-registry/io.github.pipeworx-io/who-gho/get_data, mcp-registry/io.github.rarasai/raras/get_disease_genes — capability-matched and ranked by current reliability. glama/nslc7779/korea-health-mcp-server/kohealth_get_disease_stats itself is currently "unknown".

alternative	server
mcp-registry/io.github.rarasai/raras/get_disease	io.github.rarasAI/raras	live status →
mcp-registry/io.github.rarasai/raras/get_disease_sus_coverage	io.github.rarasAI/raras	live status →
mcp-registry/io.github.andrew-sondgeroth/zipexplore-mcp/get_healthcare_profile	io.github.andrew-sondgeroth/zipexplore-mcp	live status →
mcp-registry/io.github.pipeworx-io/who-gho/get_data	io.github.pipeworx-io/who-gho	live status →
mcp-registry/io.github.rarasai/raras/get_disease_genes	io.github.rarasAI/raras	live status →
mcp-registry/fyi.medrates/mcp/search	fyi.medrates/mcp	live status →
mcp-registry/org.pinnacleblooms/ask/lookup_code	org.pinnacleblooms/ask	live status →
mcp-registry/io.github.france-care/alice-territorial/analyze_territory	io.github.France-Care/alice-territorial	live status →
mcp-registry/io.github.pipeworx-io/monarch-initiative/gene_to_disease	io.github.pipeworx-io/monarch-initiative	live status →
mcp-registry/io.github.rarasai/raras/get_disease_clinical_trials	io.github.rarasAI/raras	live status →

FAQ

What is the best alternative to glama/nslc7779/korea-health-mcp-server/kohealth_get_disease_stats?

mcp-registry/io.github.rarasai/raras/get_disease is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.rarasai/raras/get_disease_sus_coverage, mcp-registry/io.github.andrew-sondgeroth/zipexplore-mcp/get_healthcare_profile, mcp-registry/io.github.pipeworx-io/who-gho/get_data, mcp-registry/io.github.rarasai/raras/get_disease_genes. Glimind ranks alternatives by semantic similarity and live health.

Is glama/nslc7779/korea-health-mcp-server/kohealth_get_disease_stats down right now?

glama/nslc7779/korea-health-mcp-server/kohealth_get_disease_stats's current verdict is "unknown". See its live status and score at https://glimind.com/tool/glama%2Fnslc7779%2Fkorea-health-mcp-server%2Fkohealth_get_disease_stats.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/glama%2Fnslc7779%2Fkorea-health-mcp-server%2Fkohealth_get_disease_stats or MCP find_alternatives. Check glama/nslc7779/korea-health-mcp-server/kohealth_get_disease_stats's live status: https://glimind.com/tool/glama/nslc7779/korea-health-mcp-server/kohealth_get_disease_stats.