mcp-registry/domains.snooze/snooze/check_domain / alternatives
mcp-registry/domains.snooze/snooze/check_domainThe best live alternatives to mcp-registry/domains.snooze/snooze/check_domain right now are mcp-registry/io.github.pipeworx-io/domains/domain_status, mcp-registry/com.sprytools/sprytools/check_domain, mcp-registry/io.github.danboabes/mcpdomain/check_domain_availability, mcp-registry/io.github.deesmo/arch-tools-mcp/whois-lookup, mcp-registry/io.github.deesmo/arch-tools-mcp/check-domain — capability-matched and ranked by current reliability. mcp-registry/domains.snooze/snooze/check_domain itself is currently "healthy".
mcp-registry/io.github.pipeworx-io/domains/domain_status is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.sprytools/sprytools/check_domain, mcp-registry/io.github.danboabes/mcpdomain/check_domain_availability, mcp-registry/io.github.deesmo/arch-tools-mcp/whois-lookup, mcp-registry/io.github.deesmo/arch-tools-mcp/check-domain. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/domains.snooze/snooze/check_domain's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fdomains.snooze%2Fsnooze%2Fcheck_domain.
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%2Fdomains.snooze%2Fsnooze%2Fcheck_domain
or MCP find_alternatives. Check mcp-registry/domains.snooze/snooze/check_domain's live status: https://glimind.com/tool/mcp-registry/domains.snooze/snooze/check_domain.