mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record

The best live alternatives to mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record right now are mcp-registry/ru.quintadb/mcp/get_record, mcp-registry/com.quintadb/mcp/get_record, mcp-registry/ua.com.quintadb/mcp/get_record, mcp-registry/io.github.pipeworx-io/salesforce/sf_get_record, mcp-registry/io.favcrm/favcrm/get_contact — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record itself is currently "healthy".

alternative	server
mcp-registry/ru.quintadb/mcp/get_record	ru.quintadb/mcp	live status →
mcp-registry/com.quintadb/mcp/get_record	com.quintadb/mcp	live status →
mcp-registry/ua.com.quintadb/mcp/get_record	ua.com.quintadb/mcp	live status →
mcp-registry/io.github.pipeworx-io/salesforce/sf_get_record	io.github.pipeworx-io/salesforce	live status →
mcp-registry/io.favcrm/favcrm/get_contact	io.favcrm/favcrm	live status →
mcp-registry/io.github.pipeworx-io/airtable/airtable_get_record	io.github.pipeworx-io/airtable	live status →
mcp-registry/io.github.pipeworx-io/zenodo/record	io.github.pipeworx-io/zenodo	live status →
mcp-registry/io.github.benspank/pollbolt/get_response	io.github.BenSpank/pollbolt	live status →
mcp-registry/com.b2bware/mcp-server/get_media	com.b2bware/mcp-server	live status →
mcp-registry/io.github.pipeworx-io/zendesk/zd_get_user	io.github.pipeworx-io/zendesk	live status →
mcp-registry/ai.datamerge/mcp/get_contact	ai.datamerge/mcp	live status →
mcp-registry/io.famulor/famulor-mcp/get_document	io.famulor/famulor-mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record?

mcp-registry/ru.quintadb/mcp/get_record is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.quintadb/mcp/get_record, mcp-registry/ua.com.quintadb/mcp/get_record, mcp-registry/io.github.pipeworx-io/salesforce/sf_get_record, mcp-registry/io.favcrm/favcrm/get_contact. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record down right now?

mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fzoho_crm%2Fzoho_get_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%2Fzoho_crm%2Fzoho_get_record or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record.