mcp-registry/io.github.mattlsmith/navmds/semantic_search_doctors / alternatives

Live alternatives to mcp-registry/io.github.mattlsmith/navmds/semantic_search_doctors

The best live alternatives to mcp-registry/io.github.mattlsmith/navmds/semantic_search_doctors right now are mcp-registry/io.github.anteos-health/anteos-booking/search_doctors, mcp-registry/io.github.influship/influship-mcp/semantic_search_creators, mcp-registry/ai.rootdata/public-directory/search_practices, mcp-registry/io.github.anteos-health/anteos-booking/get_doctor_profile, mcp-registry/io.github.deficlow/hyperstore-mcp/ai_search — capability-matched and ranked by current reliability. mcp-registry/io.github.mattlsmith/navmds/semantic_search_doctors itself is currently "healthy".

alternative	server
mcp-registry/io.github.anteos-health/anteos-booking/search_doctors	io.github.Anteos-Health/anteos-booking	live status →
mcp-registry/io.github.influship/influship-mcp/semantic_search_creators	io.github.Influship/influship-mcp	live status →
mcp-registry/ai.rootdata/public-directory/search_practices	ai.rootdata/public-directory	live status →
mcp-registry/io.github.anteos-health/anteos-booking/get_doctor_profile	io.github.Anteos-Health/anteos-booking	live status →
mcp-registry/io.github.deficlow/hyperstore-mcp/ai_search	io.github.deficlow/hyperstore-mcp	live status →
mcp-registry/it.cup24/availability/smart_suggest_service	it.cup24/availability	live status →
mcp-registry/com.joinplexa/plexa/search_businesses	com.joinplexa/plexa	live status →
mcp-registry/me.ceki/mcp-server/search-specialists	me.ceki/mcp-server	live status →
mcp-registry/io.github.pipeworx-io/mesh/search_descriptors	io.github.pipeworx-io/mesh	live status →
mcp-registry/io.github.pipeworx-io/clinicaltables/npi_individual	io.github.pipeworx-io/clinicaltables	live status →
mcp-registry/io.github.jsonbored/metagraphed/semantic_search	io.github.JSONbored/metagraphed	live status →
mcp-registry/io.github.crindo2/gph-mcp-server/search_providers	io.github.Crindo2/gph-mcp-server	live status →

FAQ

What is the best alternative to mcp-registry/io.github.mattlsmith/navmds/semantic_search_doctors?

mcp-registry/io.github.anteos-health/anteos-booking/search_doctors is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.influship/influship-mcp/semantic_search_creators, mcp-registry/ai.rootdata/public-directory/search_practices, mcp-registry/io.github.anteos-health/anteos-booking/get_doctor_profile, mcp-registry/io.github.deficlow/hyperstore-mcp/ai_search. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.mattlsmith/navmds/semantic_search_doctors down right now?

mcp-registry/io.github.mattlsmith/navmds/semantic_search_doctors's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.mattlsmith%2Fnavmds%2Fsemantic_search_doctors.

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/mcp-registry%2Fio.github.mattlsmith%2Fnavmds%2Fsemantic_search_doctors or MCP find_alternatives. Check mcp-registry/io.github.mattlsmith/navmds/semantic_search_doctors's live status: https://glimind.com/tool/mcp-registry/io.github.mattlsmith/navmds/semantic_search_doctors.