mcp-registry/cz.salesbot/linkedin-mcp-server/delete_crm_field / alternatives
mcp-registry/cz.salesbot/linkedin-mcp-server/delete_crm_fieldThe best live alternatives to mcp-registry/cz.salesbot/linkedin-mcp-server/delete_crm_field right now are mcp-registry/io.favcrm/favcrm/delete_custom_field, mcp-registry/io.famulor/famulor-mcp/delete_lead, mcp-registry/io.favcrm/favcrm/set_custom_field_values, mcp-registry/ru.quintadb/mcp/delete_field, mcp-registry/com.quintadb/mcp/delete_field — capability-matched and ranked by current reliability. mcp-registry/cz.salesbot/linkedin-mcp-server/delete_crm_field itself is currently "healthy".
| alternative | server | |
|---|---|---|
| mcp-registry/io.favcrm/favcrm/delete_custom_field | io.favcrm/favcrm | live status → |
| mcp-registry/io.famulor/famulor-mcp/delete_lead | io.famulor/famulor-mcp | live status → |
| mcp-registry/io.favcrm/favcrm/set_custom_field_values | io.favcrm/favcrm | live status → |
| mcp-registry/ru.quintadb/mcp/delete_field | ru.quintadb/mcp | live status → |
| mcp-registry/com.quintadb/mcp/delete_field | com.quintadb/mcp | live status → |
| mcp-registry/ua.com.quintadb/mcp/delete_field | ua.com.quintadb/mcp | live status → |
| mcp-registry/io.favcrm/favcrm/create_custom_field | io.favcrm/favcrm | live status → |
| mcp-registry/io.favcrm/favcrm/list_custom_fields | io.favcrm/favcrm | live status → |
| mcp-registry/io.favcrm/favcrm/delete_deal | io.favcrm/favcrm | live status → |
| pulsemcp/adbutler/delete_data_key | AdButler | live status → |
| mcp-registry/com.adbutler/mcp-server/delete_data_key | com.adbutler/mcp-server | live status → |
| mcp-registry/io.favcrm/favcrm/delete_task | io.favcrm/favcrm | live status → |
mcp-registry/io.favcrm/favcrm/delete_custom_field is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.famulor/famulor-mcp/delete_lead, mcp-registry/io.favcrm/favcrm/set_custom_field_values, mcp-registry/ru.quintadb/mcp/delete_field, mcp-registry/com.quintadb/mcp/delete_field. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/cz.salesbot/linkedin-mcp-server/delete_crm_field's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcz.salesbot%2Flinkedin-mcp-server%2Fdelete_crm_field.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fcz.salesbot%2Flinkedin-mcp-server%2Fdelete_crm_field
or MCP find_alternatives. Check mcp-registry/cz.salesbot/linkedin-mcp-server/delete_crm_field's live status: https://glimind.com/tool/mcp-registry/cz.salesbot/linkedin-mcp-server/delete_crm_field.