mcp-registry/io.github.br0ski777/sms-validator/sms_validate_number / alternatives
mcp-registry/io.github.br0ski777/sms-validator/sms_validate_numberThe best live alternatives to mcp-registry/io.github.br0ski777/sms-validator/sms_validate_number right now are mcp-registry/io.github.br0ski777/phone-validation/phone_validate_number, mcp-registry/io.github.br0ski777/phone-validation/phone_validate_batch, mcp-registry/io.github.wavix/mcp/my_numbers_sms_update, mcp-registry/io.github.qinisolabs/qiniso/validate_phone, mcp-registry/io.github.wavix/mcp/sms_and_mms_messages_send — capability-matched and ranked by current reliability. mcp-registry/io.github.br0ski777/sms-validator/sms_validate_number itself is currently "healthy".
mcp-registry/io.github.br0ski777/phone-validation/phone_validate_number is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.br0ski777/phone-validation/phone_validate_batch, mcp-registry/io.github.wavix/mcp/my_numbers_sms_update, mcp-registry/io.github.qinisolabs/qiniso/validate_phone, mcp-registry/io.github.wavix/mcp/sms_and_mms_messages_send. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.br0ski777/sms-validator/sms_validate_number's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.br0ski777%2Fsms-validator%2Fsms_validate_number.
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.br0ski777%2Fsms-validator%2Fsms_validate_number
or MCP find_alternatives. Check mcp-registry/io.github.br0ski777/sms-validator/sms_validate_number's live status: https://glimind.com/tool/mcp-registry/io.github.br0ski777/sms-validator/sms_validate_number.