mcp-registry/io.github.wvdsh/wavedash/wavedash_validate_config / alternatives
mcp-registry/io.github.wvdsh/wavedash/wavedash_validate_configThe best live alternatives to mcp-registry/io.github.wvdsh/wavedash/wavedash_validate_config right now are pulsemcp/3tg-test-generation/validate_config, mcp-registry/dev.3tg/mcp/validate_config, mcp-registry/dev.ohmyposh/validator/validate_config, mcp-registry/com.webforj/mcp/styles_validate_tokens, mcp-registry/tools.knurl/secret-scanner/scan_for_secrets — capability-matched and ranked by current reliability. mcp-registry/io.github.wvdsh/wavedash/wavedash_validate_config itself is currently "healthy".
pulsemcp/3tg-test-generation/validate_config is the top capability-matched alternative that's live right now. Other options: mcp-registry/dev.3tg/mcp/validate_config, mcp-registry/dev.ohmyposh/validator/validate_config, mcp-registry/com.webforj/mcp/styles_validate_tokens, mcp-registry/tools.knurl/secret-scanner/scan_for_secrets. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.wvdsh/wavedash/wavedash_validate_config's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.wvdsh%2Fwavedash%2Fwavedash_validate_config.
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.wvdsh%2Fwavedash%2Fwavedash_validate_config
or MCP find_alternatives. Check mcp-registry/io.github.wvdsh/wavedash/wavedash_validate_config's live status: https://glimind.com/tool/mcp-registry/io.github.wvdsh/wavedash/wavedash_validate_config.