mcp-registry/io.github.tronsave/mcp/tronsave_get_deposit_address / alternatives
mcp-registry/io.github.tronsave/mcp/tronsave_get_deposit_addressThe best live alternatives to mcp-registry/io.github.tronsave/mcp/tronsave_get_deposit_address right now are pulsemcp/abgeordnetenwatch/recall, mcp-registry/io.github.pipeworx-io/open-notify/recall, mcp-registry/io.github.pipeworx-io/jikan/recall, mcp-registry/io.github.pipeworx-io/jargon-translator/recall, mcp-registry/io.github.pipeworx-io/jersey-opendata/recall — capability-matched and ranked by current reliability. mcp-registry/io.github.tronsave/mcp/tronsave_get_deposit_address itself is currently "healthy".
pulsemcp/abgeordnetenwatch/recall is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/open-notify/recall, mcp-registry/io.github.pipeworx-io/jikan/recall, mcp-registry/io.github.pipeworx-io/jargon-translator/recall, mcp-registry/io.github.pipeworx-io/jersey-opendata/recall. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.tronsave/mcp/tronsave_get_deposit_address's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.tronsave%2Fmcp%2Ftronsave_get_deposit_address.
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.tronsave%2Fmcp%2Ftronsave_get_deposit_address
or MCP find_alternatives. Check mcp-registry/io.github.tronsave/mcp/tronsave_get_deposit_address's live status: https://glimind.com/tool/mcp-registry/io.github.tronsave/mcp/tronsave_get_deposit_address.