mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact / alternatives

Live alternatives to mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact

The best live alternatives to mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact right now are mcp-registry/io.favcrm/favcrm/update_contact, pulsemcp/adbutler/update_contact, mcp-registry/com.adbutler/mcp-server/update_contact, mcp-registry/io.famulor/famulor-mcp/update_lead, mcp-registry/com.kaicalls/kaicalls/upsert_lead — capability-matched and ranked by current reliability. mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact itself is currently "healthy".

alternative	server
mcp-registry/io.favcrm/favcrm/update_contact	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.famulor/famulor-mcp/update_lead	io.famulor/famulor-mcp	live status →
mcp-registry/com.kaicalls/kaicalls/upsert_lead	com.kaicalls/kaicalls	live status →
mcp-registry/io.github.saloprj/dialogbrain/contacts_update	io.github.saloprj/dialogbrain	live status →
mcp-registry/tools.growthkit/revenue-intelligence/updateCampaignLead	tools.growthkit/revenue-intelligence	live status →
mcp-registry/io.github.saloprj/dialogbrain/contacts_capture_lead	io.github.saloprj/dialogbrain	live status →
mcp-registry/io.favcrm/favcrm/update_account	io.favcrm/favcrm	live status →
mcp-registry/tools.growthkit/revenue-intelligence/addCampaignLeads	tools.growthkit/revenue-intelligence	live status →
mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_list_contacts	io.github.pipeworx-io/leadconnector	live status →
mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_get_contact	io.github.pipeworx-io/leadconnector	live status →

FAQ

What is the best alternative to mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact?

mcp-registry/io.favcrm/favcrm/update_contact is the top capability-matched alternative that's live right now. Other options: pulsemcp/adbutler/update_contact, mcp-registry/com.adbutler/mcp-server/update_contact, mcp-registry/io.famulor/famulor-mcp/update_lead, mcp-registry/com.kaicalls/kaicalls/upsert_lead. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact down right now?

mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcz.salesbot%2Flinkedin-mcp-server%2Fupdate_contact.

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%2Fcz.salesbot%2Flinkedin-mcp-server%2Fupdate_contact or MCP find_alternatives. Check mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact's live status: https://glimind.com/tool/mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact.