mcp-registry/io.favcrm/favcrm/update_contact / alternatives

Live alternatives to mcp-registry/io.favcrm/favcrm/update_contact

The best live alternatives to mcp-registry/io.favcrm/favcrm/update_contact right now are mcp-registry/ai.justpublish/just-publish/update_site_file, mcp-registry/com.bankruptcyobserver/mcp/get_case_by_ein_tool, mcp-registry/io.github.mirabello-consultancy/mcp-server/get_recent_changes, mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/realestate_watch_recent_changes, mcp-registry/io.revise/mcp-server/get_recent_changes — capability-matched and ranked by current reliability. mcp-registry/io.favcrm/favcrm/update_contact itself is currently "healthy".

alternative	server
mcp-registry/ai.justpublish/just-publish/update_site_file	ai.justpublish/just-publish	live status →
mcp-registry/com.bankruptcyobserver/mcp/get_case_by_ein_tool	com.bankruptcyobserver/mcp	live status →
mcp-registry/io.github.mirabello-consultancy/mcp-server/get_recent_changes	io.github.mirabello-consultancy/mcp-server	live status →
mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/realestate_watch_recent_changes	com.mcp-revenue-empire/japan-public-ledgers	live status →
mcp-registry/io.revise/mcp-server/get_recent_changes	io.revise/mcp-server	live status →
mcp-registry/io.github.pipeworx-io/nsi-bg/recent_changes	io.github.pipeworx-io/nsi-bg	live status →
mcp-registry/io.github.pipeworx-io/twitch/recent_changes	io.github.pipeworx-io/twitch	live status →
mcp-registry/io.github.pipeworx-io/uniprot/recent_changes	io.github.pipeworx-io/uniprot	live status →
mcp-registry/io.github.pipeworx-io/lichess/recent_changes	io.github.pipeworx-io/lichess	live status →
mcp-registry/io.github.pipeworx-io/jargon-translator/recent_changes	io.github.pipeworx-io/jargon-translator	live status →
mcp-registry/io.github.pipeworx-io/usgs-earthquakes/recent_changes	io.github.pipeworx-io/usgs-earthquakes	live status →
mcp-registry/io.github.pipeworx-io/worldbank-poverty/recent_changes	io.github.pipeworx-io/worldbank-poverty	live status →

FAQ

What is the best alternative to mcp-registry/io.favcrm/favcrm/update_contact?

mcp-registry/ai.justpublish/just-publish/update_site_file is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.bankruptcyobserver/mcp/get_case_by_ein_tool, mcp-registry/io.github.mirabello-consultancy/mcp-server/get_recent_changes, mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/realestate_watch_recent_changes, mcp-registry/io.revise/mcp-server/get_recent_changes. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.favcrm/favcrm/update_contact down right now?

mcp-registry/io.favcrm/favcrm/update_contact's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.favcrm%2Ffavcrm%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%2Fio.favcrm%2Ffavcrm%2Fupdate_contact or MCP find_alternatives. Check mcp-registry/io.favcrm/favcrm/update_contact's live status: https://glimind.com/tool/mcp-registry/io.favcrm/favcrm/update_contact.