mcp-registry/io.github.bitofacoder/omni-mcp-server/slack_send_message / alternatives
mcp-registry/io.github.bitofacoder/omni-mcp-server/slack_send_messageThe best live alternatives to mcp-registry/io.github.bitofacoder/omni-mcp-server/slack_send_message right now are mcp-registry/io.github.pipeworx-io/slack_connect/slack_send_message, mcp-registry/dev.metamesh-uga/metamesh-uga/slack — capability-matched and ranked by current reliability. mcp-registry/io.github.bitofacoder/omni-mcp-server/slack_send_message itself is currently "unknown".
| alternative | server | |
|---|---|---|
| mcp-registry/io.github.pipeworx-io/slack_connect/slack_send_message | io.github.pipeworx-io/slack_connect | live status → |
| mcp-registry/dev.metamesh-uga/metamesh-uga/slack | dev.metamesh-uga/metamesh-uga | live status → |
mcp-registry/io.github.pipeworx-io/slack_connect/slack_send_message is the top capability-matched alternative that's live right now. Other options: mcp-registry/dev.metamesh-uga/metamesh-uga/slack. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.bitofacoder/omni-mcp-server/slack_send_message's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.bitofacoder%2Fomni-mcp-server%2Fslack_send_message.
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%2Fio.github.bitofacoder%2Fomni-mcp-server%2Fslack_send_message
or MCP find_alternatives. Check mcp-registry/io.github.bitofacoder/omni-mcp-server/slack_send_message's live status: https://glimind.com/tool/mcp-registry/io.github.bitofacoder/omni-mcp-server/slack_send_message.