npm/-supernova123/system-monitoring-mcp-server/login_history / alternatives

Live alternatives to npm/-supernova123/system-monitoring-mcp-server/login_history

The best live alternatives to npm/-supernova123/system-monitoring-mcp-server/login_history right now are mcp-registry/io.github.benseverndev-oss/goldenmatch/identity_history, mcp-registry/com.adbutler/mcp-server/get_event_logs — capability-matched and ranked by current reliability. npm/-supernova123/system-monitoring-mcp-server/login_history itself is currently "unknown".

alternative	server
mcp-registry/io.github.benseverndev-oss/goldenmatch/identity_history	io.github.benseverndev-oss/goldenmatch	live status →
mcp-registry/com.adbutler/mcp-server/get_event_logs	com.adbutler/mcp-server	live status →

FAQ

What is the best alternative to npm/-supernova123/system-monitoring-mcp-server/login_history?

mcp-registry/io.github.benseverndev-oss/goldenmatch/identity_history is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.adbutler/mcp-server/get_event_logs. Glimind ranks alternatives by semantic similarity and live health.

Is npm/-supernova123/system-monitoring-mcp-server/login_history down right now?

npm/-supernova123/system-monitoring-mcp-server/login_history's current verdict is "unknown". See its live status and score at https://glimind.com/tool/npm%2F-supernova123%2Fsystem-monitoring-mcp-server%2Flogin_history.

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/npm%2F-supernova123%2Fsystem-monitoring-mcp-server%2Flogin_history or MCP find_alternatives. Check npm/-supernova123/system-monitoring-mcp-server/login_history's live status: https://glimind.com/tool/npm/-supernova123/system-monitoring-mcp-server/login_history.