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

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

The best live alternatives to mcp-registry/cz.salesbot/linkedin-mcp-server/list_inbox_chats right now are mcp-registry/io.github.pipeworx-io/gdelt/list_subscriptions, mcp-registry/io.github.pipeworx-io/arcgis-johnsoncity/list_subscriptions, mcp-registry/io.github.pipeworx-io/arcgis-linncounty/list_subscriptions, mcp-registry/io.github.pipeworx-io/arcgis-lakecountyil/list_subscriptions, mcp-registry/io.github.pipeworx-io/iso-codes/list_subscriptions — capability-matched and ranked by current reliability. mcp-registry/cz.salesbot/linkedin-mcp-server/list_inbox_chats itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/gdelt/list_subscriptions	io.github.pipeworx-io/gdelt	live status →
mcp-registry/io.github.pipeworx-io/arcgis-johnsoncity/list_subscriptions	io.github.pipeworx-io/arcgis-johnsoncity	live status →
mcp-registry/io.github.pipeworx-io/arcgis-linncounty/list_subscriptions	io.github.pipeworx-io/arcgis-linncounty	live status →
mcp-registry/io.github.pipeworx-io/arcgis-lakecountyil/list_subscriptions	io.github.pipeworx-io/arcgis-lakecountyil	live status →
mcp-registry/io.github.pipeworx-io/iso-codes/list_subscriptions	io.github.pipeworx-io/iso-codes	live status →
mcp-registry/io.github.pipeworx-io/scream-void/list_subscriptions	io.github.pipeworx-io/scream-void	live status →
mcp-registry/io.github.pipeworx-io/scryfall/list_subscriptions	io.github.pipeworx-io/scryfall	live status →
mcp-registry/io.github.pipeworx-io/taginfo/list_subscriptions	io.github.pipeworx-io/taginfo	live status →
mcp-registry/io.github.pipeworx-io/tarot-draw/list_subscriptions	io.github.pipeworx-io/tarot-draw	live status →
mcp-registry/io.github.pipeworx-io/gemini-crypto/list_subscriptions	io.github.pipeworx-io/gemini-crypto	live status →
mcp-registry/io.github.pipeworx-io/dogceo/list_subscriptions	io.github.pipeworx-io/dogceo	live status →
mcp-registry/io.github.pipeworx-io/digimon/list_subscriptions	io.github.pipeworx-io/digimon	live status →

FAQ

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

mcp-registry/io.github.pipeworx-io/gdelt/list_subscriptions is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/arcgis-johnsoncity/list_subscriptions, mcp-registry/io.github.pipeworx-io/arcgis-linncounty/list_subscriptions, mcp-registry/io.github.pipeworx-io/arcgis-lakecountyil/list_subscriptions, mcp-registry/io.github.pipeworx-io/iso-codes/list_subscriptions. Glimind ranks alternatives by semantic similarity and live health.

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

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

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