mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context / alternatives

Live alternatives to mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context

The best live alternatives to mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context right now are mcp-registry/io.github.peterjduffy/parsley-mcp/get_lead_enrichment, mcp-registry/io.github.pipeworx-io/close-crm/close_get_lead, mcp-registry/com.kaicalls/kaicalls/get_lead, mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_get_contact, mcp-registry/io.corpusiq/multi-source-mcp/close_connector — capability-matched and ranked by current reliability. mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context itself is currently "healthy".

alternative	server
mcp-registry/io.github.peterjduffy/parsley-mcp/get_lead_enrichment	io.github.peterjduffy/parsley-mcp	live status →
mcp-registry/io.github.pipeworx-io/close-crm/close_get_lead	io.github.pipeworx-io/close-crm	live status →
mcp-registry/com.kaicalls/kaicalls/get_lead	com.kaicalls/kaicalls	live status →
mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_get_contact	io.github.pipeworx-io/leadconnector	live status →
mcp-registry/io.corpusiq/multi-source-mcp/close_connector	io.corpusiq/multi-source-mcp	live status →
mcp-registry/tools.growthkit/revenue-intelligence/getTopLeads	tools.growthkit/revenue-intelligence	live status →
mcp-registry/io.github.comehomeai/move-helper/get-lead-status	io.github.ComeHomeAI/move-helper	live status →
mcp-registry/com.kaicalls/kaicalls/upsert_lead	com.kaicalls/kaicalls	live status →
mcp-registry/com.kaicalls/kaicalls/list_leads	com.kaicalls/kaicalls	live status →
mcp-registry/io.github.pipeworx-io/odoo/odoo_list_crm_leads	io.github.pipeworx-io/odoo	live status →
mcp-registry/tools.growthkit/revenue-intelligence/scoreLeads	tools.growthkit/revenue-intelligence	live status →
mcp-registry/tools.growthkit/revenue-intelligence/getCampaignLeadFields	tools.growthkit/revenue-intelligence	live status →

FAQ

What is the best alternative to mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context?

mcp-registry/io.github.peterjduffy/parsley-mcp/get_lead_enrichment is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/close-crm/close_get_lead, mcp-registry/com.kaicalls/kaicalls/get_lead, mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_get_contact, mcp-registry/io.corpusiq/multi-source-mcp/close_connector. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context down right now?

mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcz.salesbot%2Flinkedin-mcp-server%2Fget_lead_context.

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%2Fcz.salesbot%2Flinkedin-mcp-server%2Fget_lead_context or MCP find_alternatives. Check mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context's live status: https://glimind.com/tool/mcp-registry/cz.salesbot/linkedin-mcp-server/get_lead_context.