mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_get_contact / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_get_contact

The best live alternatives to mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_get_contact right now are mcp-registry/io.github.pipeworx-io/activecampaign/get_contact, mcp-registry/io.github.pipeworx-io/intercom/ic_get_contact, mcp-registry/io.github.pipeworx-io/close-crm/close_get_lead, mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context, mcp-registry/cz.salesbot/linkedin-mcp-server/list_contacts — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_get_contact itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/activecampaign/get_contact	io.github.pipeworx-io/activecampaign	live status →
mcp-registry/io.github.pipeworx-io/intercom/ic_get_contact	io.github.pipeworx-io/intercom	live status →
mcp-registry/io.github.pipeworx-io/close-crm/close_get_lead	io.github.pipeworx-io/close-crm	live status →
mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context	cz.salesbot/linkedin-mcp-server	live status →
mcp-registry/cz.salesbot/linkedin-mcp-server/list_contacts	cz.salesbot/linkedin-mcp-server	live status →
pulsemcp/adbutler/get_contact	AdButler	live status →
mcp-registry/com.adbutler/mcp-server/get_contact	com.adbutler/mcp-server	live status →
mcp-registry/io.favcrm/favcrm/get_contact	io.favcrm/favcrm	live status →
mcp-registry/cz.salesbot/linkedin-mcp-server/update_contact	cz.salesbot/linkedin-mcp-server	live status →
mcp-registry/io.corpusiq/multi-source-mcp/close_connector	io.corpusiq/multi-source-mcp	live status →
mcp-registry/io.github.pipeworx-io/hubspot/hs_get_contact	io.github.pipeworx-io/hubspot	live status →
mcp-registry/cz.salesbot/linkedin-mcp-server/get_contact_profile	cz.salesbot/linkedin-mcp-server	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_get_contact?

mcp-registry/io.github.pipeworx-io/activecampaign/get_contact is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/intercom/ic_get_contact, mcp-registry/io.github.pipeworx-io/close-crm/close_get_lead, mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context, mcp-registry/cz.salesbot/linkedin-mcp-server/list_contacts. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_get_contact down right now?

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