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

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

The best live alternatives to mcp-registry/io.github.mattlsmith/navmds/search_doctors right now are mcp-registry/info.vetclinic/directory/find_specialists_by_procedure, mcp-registry/fyi.medrates/mcp/search, mcp-registry/io.github.blackboxfoundry/livedatalink/npi_search_specialty, mcp-registry/io.github.anteos-health/anteos-booking/search_doctors, mcp-registry/ai.rootdata/public-directory/search_practices — capability-matched and ranked by current reliability. mcp-registry/io.github.mattlsmith/navmds/search_doctors itself is currently "healthy".

alternativeserver
mcp-registry/info.vetclinic/directory/find_specialists_by_procedureinfo.vetclinic/directorylive status →
mcp-registry/fyi.medrates/mcp/searchfyi.medrates/mcplive status →
mcp-registry/io.github.blackboxfoundry/livedatalink/npi_search_specialtyio.github.blackboxfoundry/livedatalinklive status →
mcp-registry/io.github.anteos-health/anteos-booking/search_doctorsio.github.Anteos-Health/anteos-bookinglive status →
mcp-registry/ai.rootdata/public-directory/search_practicesai.rootdata/public-directorylive status →
mcp-registry/io.github.blackboxfoundry/livedatalink/npi_search_providerio.github.blackboxfoundry/livedatalinklive status →
mcp-registry/com.joinplexa/plexa/search_businessescom.joinplexa/plexalive status →
mcp-registry/info.vetclinic/directory/search_clinicsinfo.vetclinic/directorylive status →
mcp-registry/io.github.pipeworx-io/clinicaltables/proceduresio.github.pipeworx-io/clinicaltableslive status →
mcp-registry/io.github.pipeworx-io/clinicaltables/npi_individualio.github.pipeworx-io/clinicaltableslive status →
mcp-registry/io.github.crindo2/gph-mcp-server/search_providersio.github.Crindo2/gph-mcp-serverlive status →
mcp-registry/io.github.blackboxfoundry/livedatalink/local_searchio.github.blackboxfoundry/livedatalinklive status →

FAQ

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

mcp-registry/info.vetclinic/directory/find_specialists_by_procedure is the top capability-matched alternative that's live right now. Other options: mcp-registry/fyi.medrates/mcp/search, mcp-registry/io.github.blackboxfoundry/livedatalink/npi_search_specialty, mcp-registry/io.github.anteos-health/anteos-booking/search_doctors, mcp-registry/ai.rootdata/public-directory/search_practices. Glimind ranks alternatives by semantic similarity and live health.

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

mcp-registry/io.github.mattlsmith/navmds/search_doctors's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.mattlsmith%2Fnavmds%2Fsearch_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%2Fsearch_doctors or MCP find_alternatives. Check mcp-registry/io.github.mattlsmith/navmds/search_doctors's live status: https://glimind.com/tool/mcp-registry/io.github.mattlsmith/navmds/search_doctors.