mcp-registry/io.github.crindo2/gph-mcp-server/get_provider_detail / alternatives
mcp-registry/io.github.crindo2/gph-mcp-server/get_provider_detailThe best live alternatives to mcp-registry/io.github.crindo2/gph-mcp-server/get_provider_detail right now are mcp-registry/com.getcaboo/caboo/get_provider, mcp-registry/io.github.oliverhpage/stoop/provider_profile, mcp-registry/io.github.localprodev/local-services/get_provider, mcp-registry/ai.rootdata/public-directory/get_practice_profile, mcp-registry/io.apis/apis-io/get_provider — capability-matched and ranked by current reliability. mcp-registry/io.github.crindo2/gph-mcp-server/get_provider_detail itself is currently "healthy".
mcp-registry/com.getcaboo/caboo/get_provider is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.oliverhpage/stoop/provider_profile, mcp-registry/io.github.localprodev/local-services/get_provider, mcp-registry/ai.rootdata/public-directory/get_practice_profile, mcp-registry/io.apis/apis-io/get_provider. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.crindo2/gph-mcp-server/get_provider_detail's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.crindo2%2Fgph-mcp-server%2Fget_provider_detail.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.crindo2%2Fgph-mcp-server%2Fget_provider_detail
or MCP find_alternatives. Check mcp-registry/io.github.crindo2/gph-mcp-server/get_provider_detail's live status: https://glimind.com/tool/mcp-registry/io.github.crindo2/gph-mcp-server/get_provider_detail.