mcp-registry/io.github.pipeworx-io/salesforce/sf_update_record / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/salesforce/sf_update_record

The best live alternatives to mcp-registry/io.github.pipeworx-io/salesforce/sf_update_record right now are mcp-registry/io.favcrm/favcrm/update_contact, mcp-registry/io.github.trackingtime/mcp-server/update_project, mcp-registry/com.compoid/mcp-server/Compoid_update_record, mcp-registry/io.favcrm/favcrm/update_account, pulsemcp/adbutler/update_contact — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/salesforce/sf_update_record itself is currently "healthy".

alternative	server
mcp-registry/io.favcrm/favcrm/update_contact	io.favcrm/favcrm	live status →
mcp-registry/io.github.trackingtime/mcp-server/update_project	io.github.TrackingTime/mcp-server	live status →
mcp-registry/com.compoid/mcp-server/Compoid_update_record	com.compoid/mcp-server	live status →
mcp-registry/io.favcrm/favcrm/update_account	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/tools.growthkit/revenue-intelligence/updateCampaignLead	tools.growthkit/revenue-intelligence	live status →
mcp-registry/com.b2bware/mcp-server/update_customer	com.b2bware/mcp-server	live status →
mcp-registry/ru.quintadb/mcp/bulk_update_records	ru.quintadb/mcp	live status →
mcp-registry/com.quintadb/mcp/bulk_update_records	com.quintadb/mcp	live status →
mcp-registry/ua.com.quintadb/mcp/bulk_update_records	ua.com.quintadb/mcp	live status →
mcp-registry/com.lodikidsactivities/lodi-kids-activities/org_update_program	com.lodikidsactivities/lodi-kids-activities	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/salesforce/sf_update_record?

mcp-registry/io.favcrm/favcrm/update_contact is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.trackingtime/mcp-server/update_project, mcp-registry/com.compoid/mcp-server/Compoid_update_record, mcp-registry/io.favcrm/favcrm/update_account, pulsemcp/adbutler/update_contact. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/salesforce/sf_update_record down right now?

mcp-registry/io.github.pipeworx-io/salesforce/sf_update_record's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fsalesforce%2Fsf_update_record.

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.pipeworx-io%2Fsalesforce%2Fsf_update_record or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/salesforce/sf_update_record's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/salesforce/sf_update_record.