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

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

The best live alternatives to mcp-registry/cz.salesbot/linkedin-mcp-server/get_contact_profile right now are mcp-registry/io.github.saloprj/dialogbrain/contacts_profile, mcp-registry/io.github.pipeworx-io/hubspot/hs_get_contact, mcp-registry/io.github.pipeworx-io/klaviyo/klaviyo_get_profile, mcp-registry/io.github.pipeworx-io/intercom/ic_get_contact, mcp-registry/io.github.pipeworx-io/activecampaign/get_contact — capability-matched and ranked by current reliability. mcp-registry/cz.salesbot/linkedin-mcp-server/get_contact_profile itself is currently "healthy".

alternative	server
mcp-registry/io.github.saloprj/dialogbrain/contacts_profile	io.github.saloprj/dialogbrain	live status →
mcp-registry/io.github.pipeworx-io/hubspot/hs_get_contact	io.github.pipeworx-io/hubspot	live status →
mcp-registry/io.github.pipeworx-io/klaviyo/klaviyo_get_profile	io.github.pipeworx-io/klaviyo	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/activecampaign/get_contact	io.github.pipeworx-io/activecampaign	live status →
mcp-registry/io.github.pipeworx-io/leadconnector/leadconnector_get_contact	io.github.pipeworx-io/leadconnector	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.github.pipeworx-io/ashby/ashby_get_candidate	io.github.pipeworx-io/ashby	live status →
mcp-registry/ai.com.mcp/linkedin/getPersonProfile	ai.com.mcp/linkedin	live status →
mcp-registry/io.calvix/mcp/get_contact_info	io.calvix/mcp	live status →
mcp-registry/com.po6/mailbox/get_email_list_contacts	com.po6/mailbox	live status →

FAQ

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

mcp-registry/io.github.saloprj/dialogbrain/contacts_profile is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/hubspot/hs_get_contact, mcp-registry/io.github.pipeworx-io/klaviyo/klaviyo_get_profile, mcp-registry/io.github.pipeworx-io/intercom/ic_get_contact, mcp-registry/io.github.pipeworx-io/activecampaign/get_contact. Glimind ranks alternatives by semantic similarity and live health.

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

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

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_contact_profile or MCP find_alternatives. Check mcp-registry/cz.salesbot/linkedin-mcp-server/get_contact_profile's live status: https://glimind.com/tool/mcp-registry/cz.salesbot/linkedin-mcp-server/get_contact_profile.