mcp-registry/io.github.cturkieh/france-data-mcp/professionnels_in_radius / alternatives

Live alternatives to mcp-registry/io.github.cturkieh/france-data-mcp/professionnels_in_radius

The best live alternatives to mcp-registry/io.github.cturkieh/france-data-mcp/professionnels_in_radius right now are mcp-registry/io.github.onenicolas/mcp-service-public/consulter_acces_soins, mcp-registry/io.github.france-care/alice-territorial/analyze_territory, mcp-registry/io.github.france-care/alice-territorial/search_health_infrastructure, mcp-registry/io.github.anteos-health/anteos-booking/get_doctor_profile, mcp-registry/io.github.anteos-health/anteos-booking/search_doctors — capability-matched and ranked by current reliability. mcp-registry/io.github.cturkieh/france-data-mcp/professionnels_in_radius itself is currently "healthy".

alternative	server
mcp-registry/io.github.onenicolas/mcp-service-public/consulter_acces_soins	io.github.OneNicolas/mcp-service-public	live status →
mcp-registry/io.github.france-care/alice-territorial/analyze_territory	io.github.France-Care/alice-territorial	live status →
mcp-registry/io.github.france-care/alice-territorial/search_health_infrastructure	io.github.France-Care/alice-territorial	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.anteos-health/anteos-booking/search_doctors	io.github.Anteos-Health/anteos-booking	live status →
mcp-registry/io.github.pipeworx-io/entreprises-fr/nearby	io.github.pipeworx-io/entreprises-fr	live status →
mcp-registry/io.github.wellknownmcp/ia-asso/search_near_location	io.github.wellknownmcp/ia-asso	live status →
mcp-registry/io.github.france-care/alice-territorial/compare_territories	io.github.France-Care/alice-territorial	live status →
mcp-registry/io.github.onenicolas/mcp-service-public/rechercher_service_local	io.github.OneNicolas/mcp-service-public	live status →
mcp-registry/io.github.entia-systems-core/entity-verification/professional_lookup	io.github.entia-systems-core/entity-verification	live status →
mcp-registry/io.github.onenicolas/mcp-service-public/rechercher	io.github.OneNicolas/mcp-service-public	live status →
mcp-registry/io.github.onenicolas/mcp-service-public/consulter_zonage_immobilier	io.github.OneNicolas/mcp-service-public	live status →

FAQ

What is the best alternative to mcp-registry/io.github.cturkieh/france-data-mcp/professionnels_in_radius?

mcp-registry/io.github.onenicolas/mcp-service-public/consulter_acces_soins is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.france-care/alice-territorial/analyze_territory, mcp-registry/io.github.france-care/alice-territorial/search_health_infrastructure, mcp-registry/io.github.anteos-health/anteos-booking/get_doctor_profile, mcp-registry/io.github.anteos-health/anteos-booking/search_doctors. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.cturkieh/france-data-mcp/professionnels_in_radius down right now?

mcp-registry/io.github.cturkieh/france-data-mcp/professionnels_in_radius's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.cturkieh%2Ffrance-data-mcp%2Fprofessionnels_in_radius.

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.cturkieh%2Ffrance-data-mcp%2Fprofessionnels_in_radius or MCP find_alternatives. Check mcp-registry/io.github.cturkieh/france-data-mcp/professionnels_in_radius's live status: https://glimind.com/tool/mcp-registry/io.github.cturkieh/france-data-mcp/professionnels_in_radius.