mcp-registry/io.github.aistatusdashboard/aistatusdashboard/incidents.get / alternatives

Live alternatives to mcp-registry/io.github.aistatusdashboard/aistatusdashboard/incidents.get

The best live alternatives to mcp-registry/io.github.aistatusdashboard/aistatusdashboard/incidents.get right now are mcp-registry/io.github.pipeworx-io/ai-incident-db/get_incident, mcp-registry/io.github.jsonbored/metagraphed/get_global_incidents, mcp-registry/com.claribi/mcp-server/get_report, mcp-registry/io.github.benspank/pollbolt/get_response, mcp-registry/io.github.xbt786/hipaa-agent/get_incidents — capability-matched and ranked by current reliability. mcp-registry/io.github.aistatusdashboard/aistatusdashboard/incidents.get itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/ai-incident-db/get_incident	io.github.pipeworx-io/ai-incident-db	live status →
mcp-registry/io.github.jsonbored/metagraphed/get_global_incidents	io.github.JSONbored/metagraphed	live status →
mcp-registry/com.claribi/mcp-server/get_report	com.claribi/mcp-server	live status →
mcp-registry/io.github.benspank/pollbolt/get_response	io.github.BenSpank/pollbolt	live status →
mcp-registry/io.github.xbt786/hipaa-agent/get_incidents	io.github.xbt786/hipaa-agent	live status →
mcp-registry/io.github.trackingtime/mcp-server/get_event	io.github.TrackingTime/mcp-server	live status →
mcp-registry/io.famulor/famulor-mcp/get_call	io.famulor/famulor-mcp	live status →
mcp-registry/eu.hlido/mcp/get_incidents	eu.hlido/mcp	live status →
mcp-registry/io.favcrm/favcrm/get_contact	io.favcrm/favcrm	live status →
mcp-registry/io.github.lazymac2x/ai-provider-status/get_incidents	io.github.lazymac2x/ai-provider-status	live status →
mcp-registry/com.axiorank/axiorank/axiorank_get_incident	com.axiorank/axiorank	live status →
mcp-registry/io.github.pipeworx-io/nasa-eonet/get_event	io.github.pipeworx-io/nasa-eonet	live status →

FAQ

What is the best alternative to mcp-registry/io.github.aistatusdashboard/aistatusdashboard/incidents.get?

mcp-registry/io.github.pipeworx-io/ai-incident-db/get_incident is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.jsonbored/metagraphed/get_global_incidents, mcp-registry/com.claribi/mcp-server/get_report, mcp-registry/io.github.benspank/pollbolt/get_response, mcp-registry/io.github.xbt786/hipaa-agent/get_incidents. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.aistatusdashboard/aistatusdashboard/incidents.get down right now?

mcp-registry/io.github.aistatusdashboard/aistatusdashboard/incidents.get's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.aistatusdashboard%2Faistatusdashboard%2Fincidents.get.

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.aistatusdashboard%2Faistatusdashboard%2Fincidents.get or MCP find_alternatives. Check mcp-registry/io.github.aistatusdashboard/aistatusdashboard/incidents.get's live status: https://glimind.com/tool/mcp-registry/io.github.aistatusdashboard/aistatusdashboard/incidents.get.