mcp-registry/io.github.pipeworx-io/ai-incident-db/list_taxonomies / alternatives
mcp-registry/io.github.pipeworx-io/ai-incident-db/list_taxonomiesThe best live alternatives to mcp-registry/io.github.pipeworx-io/ai-incident-db/list_taxonomies right now are mcp-registry/io.tooloracle/incidentoracle/classify_incident, mcp-registry/com.100hires/100hires/hires_list_categories, pulsemcp/100hires/hires_list_categories, mcp-registry/io.github.pipeworx-io/seatgeek/taxonomies, mcp-registry/io.favcrm/favcrm/list_service_categories — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/ai-incident-db/list_taxonomies itself is currently "healthy".
mcp-registry/io.tooloracle/incidentoracle/classify_incident is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.100hires/100hires/hires_list_categories, pulsemcp/100hires/hires_list_categories, mcp-registry/io.github.pipeworx-io/seatgeek/taxonomies, mcp-registry/io.favcrm/favcrm/list_service_categories. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.pipeworx-io/ai-incident-db/list_taxonomies's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fai-incident-db%2Flist_taxonomies.
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.pipeworx-io%2Fai-incident-db%2Flist_taxonomies
or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/ai-incident-db/list_taxonomies's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/ai-incident-db/list_taxonomies.