mcp-registry/eu.hlido/mcp/get_incidents / alternatives

Live alternatives to mcp-registry/eu.hlido/mcp/get_incidents

The best live alternatives to mcp-registry/eu.hlido/mcp/get_incidents right now are mcp-registry/io.github.jsonbored/metagraphed/get_global_incidents, mcp-registry/io.github.cuecrux/vaultcrux-memory-core/get_incident_context, mcp-registry/io.github.pipeworx-io/ai-incident-db/get_incident, mcp-registry/io.github.imviky-ctrl/tickerr/report_incident, mcp-registry/io.github.lazymac2x/ai-provider-status/get_incidents — capability-matched and ranked by current reliability. mcp-registry/eu.hlido/mcp/get_incidents itself is currently "healthy".

alternative	server
mcp-registry/io.github.jsonbored/metagraphed/get_global_incidents	io.github.JSONbored/metagraphed	live status →
mcp-registry/io.github.cuecrux/vaultcrux-memory-core/get_incident_context	io.github.CueCrux/vaultcrux-memory-core	live status →
mcp-registry/io.github.pipeworx-io/ai-incident-db/get_incident	io.github.pipeworx-io/ai-incident-db	live status →
mcp-registry/io.github.imviky-ctrl/tickerr/report_incident	io.github.imviky-ctrl/tickerr	live status →
mcp-registry/io.github.lazymac2x/ai-provider-status/get_incidents	io.github.lazymac2x/ai-provider-status	live status →
mcp-registry/io.tooloracle/incidentoracle/incident_stats	io.tooloracle/incidentoracle	live status →
mcp-registry/io.tooloracle/incidentoracle/incident_log	io.tooloracle/incidentoracle	live status →
mcp-registry/io.github.xbt786/hipaa-agent/get_incidents	io.github.xbt786/hipaa-agent	live status →
pulsemcp/x711/x711_self_audit	x711	live status →
mcp-registry/io.github.0580iris-lang/x711-gas-station/x711_self_audit	io.github.0580iris-lang/x711-gas-station	live status →
mcp-registry/io.huntertech/vendor-insights/get_all_vendor_incidents	io.huntertech/vendor-insights	live status →
mcp-registry/io.github.pipeworx-io/ai-incident-db/list_recent	io.github.pipeworx-io/ai-incident-db	live status →

FAQ

What is the best alternative to mcp-registry/eu.hlido/mcp/get_incidents?

mcp-registry/io.github.jsonbored/metagraphed/get_global_incidents is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.cuecrux/vaultcrux-memory-core/get_incident_context, mcp-registry/io.github.pipeworx-io/ai-incident-db/get_incident, mcp-registry/io.github.imviky-ctrl/tickerr/report_incident, mcp-registry/io.github.lazymac2x/ai-provider-status/get_incidents. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/eu.hlido/mcp/get_incidents down right now?

mcp-registry/eu.hlido/mcp/get_incidents's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Feu.hlido%2Fmcp%2Fget_incidents.

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%2Feu.hlido%2Fmcp%2Fget_incidents or MCP find_alternatives. Check mcp-registry/eu.hlido/mcp/get_incidents's live status: https://glimind.com/tool/mcp-registry/eu.hlido/mcp/get_incidents.