mcp-registry/io.github.wavix/mcp/sip_trunks_update / alternatives

Live alternatives to mcp-registry/io.github.wavix/mcp/sip_trunks_update

The best live alternatives to mcp-registry/io.github.wavix/mcp/sip_trunks_update right now are mcp-registry/io.famulor/famulor-mcp/update_sip_trunk, mcp-registry/io.famulor/famulor-mcp/delete_sip_trunk, mcp-registry/io.famulor/famulor-mcp/create_sip_trunk, mcp-registry/io.famulor/famulor-mcp/get_sip_trunk, mcp-registry/io.famulor/famulor-mcp/list_sip_trunks — capability-matched and ranked by current reliability. mcp-registry/io.github.wavix/mcp/sip_trunks_update itself is currently "healthy".

alternative	server
mcp-registry/io.famulor/famulor-mcp/update_sip_trunk	io.famulor/famulor-mcp	live status →
mcp-registry/io.famulor/famulor-mcp/delete_sip_trunk	io.famulor/famulor-mcp	live status →
mcp-registry/io.famulor/famulor-mcp/create_sip_trunk	io.famulor/famulor-mcp	live status →
mcp-registry/io.famulor/famulor-mcp/get_sip_trunk	io.famulor/famulor-mcp	live status →
mcp-registry/io.famulor/famulor-mcp/list_sip_trunks	io.famulor/famulor-mcp	live status →
mcp-registry/cloud.theprotocol/registry/theprotocol_updatePeerSlashConfig	cloud.theprotocol/registry	live status →
mcp-registry/io.github.deepakumarsubbian/orbiteos/update_plugin_config	io.github.DeepakumarSubbian/orbiteos	live status →
mcp-registry/io.github.tronsave/mcp/tronsave_update_auto_sell_setting	io.github.tronsave/mcp	live status →
mcp-registry/io.famulor/famulor-mcp/update_mid_call_tool	io.famulor/famulor-mcp	live status →
mcp-registry/app.saber.mcp/saber/subscription_actions-update	app.saber.mcp/saber	live status →
mcp-registry/com.googleapis.sqladmin/mcp/update_instance	com.googleapis.sqladmin/mcp	live status →
mcp-registry/app.saber.mcp/saber/signal_subscriptions-update	app.saber.mcp/saber	live status →

FAQ

What is the best alternative to mcp-registry/io.github.wavix/mcp/sip_trunks_update?

mcp-registry/io.famulor/famulor-mcp/update_sip_trunk is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.famulor/famulor-mcp/delete_sip_trunk, mcp-registry/io.famulor/famulor-mcp/create_sip_trunk, mcp-registry/io.famulor/famulor-mcp/get_sip_trunk, mcp-registry/io.famulor/famulor-mcp/list_sip_trunks. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.wavix/mcp/sip_trunks_update down right now?

mcp-registry/io.github.wavix/mcp/sip_trunks_update's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.wavix%2Fmcp%2Fsip_trunks_update.

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%2Fio.github.wavix%2Fmcp%2Fsip_trunks_update or MCP find_alternatives. Check mcp-registry/io.github.wavix/mcp/sip_trunks_update's live status: https://glimind.com/tool/mcp-registry/io.github.wavix/mcp/sip_trunks_update.