mcp-registry/io.github.dynamitecircle/dc/locator_settings_update / alternatives

Live alternatives to mcp-registry/io.github.dynamitecircle/dc/locator_settings_update

The best live alternatives to mcp-registry/io.github.dynamitecircle/dc/locator_settings_update right now are mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact, mcp-registry/io.github.tettertotter/fundinglandscape/update_saved_search, mcp-registry/io.favcrm/favcrm/update_contact, mcp-registry/cloud.theprotocol/registry/theprotocol_updateOrganization, pulsemcp/adbutler/update_email_zone — capability-matched and ranked by current reliability. mcp-registry/io.github.dynamitecircle/dc/locator_settings_update itself is currently "healthy".

alternative	server
mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact	cz.salesbot/linkedin-mcp-server	live status →
mcp-registry/io.github.tettertotter/fundinglandscape/update_saved_search	io.github.tettertotter/fundinglandscape	live status →
mcp-registry/io.favcrm/favcrm/update_contact	io.favcrm/favcrm	live status →
mcp-registry/cloud.theprotocol/registry/theprotocol_updateOrganization	cloud.theprotocol/registry	live status →
pulsemcp/adbutler/update_email_zone	AdButler	live status →
mcp-registry/com.adbutler/mcp-server/update_email_zone	com.adbutler/mcp-server	live status →
mcp-registry/io.favcrm/favcrm/update_promotion	io.favcrm/favcrm	live status →
mcp-registry/io.stablebaseline/sb/updateOrgSettings	io.stablebaseline/sb	live status →
mcp-registry/io.favcrm/favcrm/update_service	io.favcrm/favcrm	live status →
pulsemcp/adbutler/update_contact	AdButler	live status →
mcp-registry/com.adbutler/mcp-server/update_contact	com.adbutler/mcp-server	live status →
mcp-registry/io.favcrm/favcrm/update_booking_settings	io.favcrm/favcrm	live status →

FAQ

What is the best alternative to mcp-registry/io.github.dynamitecircle/dc/locator_settings_update?

mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.tettertotter/fundinglandscape/update_saved_search, mcp-registry/io.favcrm/favcrm/update_contact, mcp-registry/cloud.theprotocol/registry/theprotocol_updateOrganization, pulsemcp/adbutler/update_email_zone. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.dynamitecircle/dc/locator_settings_update down right now?

mcp-registry/io.github.dynamitecircle/dc/locator_settings_update's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.dynamitecircle%2Fdc%2Flocator_settings_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.dynamitecircle%2Fdc%2Flocator_settings_update or MCP find_alternatives. Check mcp-registry/io.github.dynamitecircle/dc/locator_settings_update's live status: https://glimind.com/tool/mcp-registry/io.github.dynamitecircle/dc/locator_settings_update.