mcp-registry/network.tenzro/tenzro/resolve_username / alternatives

Live alternatives to mcp-registry/network.tenzro/tenzro/resolve_username

The best live alternatives to mcp-registry/network.tenzro/tenzro/resolve_username right now are mcp-registry/io.github.pipeworx-io/roblox/user_by_username, mcp-registry/io.github.srotzin/hive-mcp-identity/resolve_did, mcp-registry/io.github.farestrabs/agentnet/resolve_identity, mcp-registry/io.github.majorelalexis-stack/maxia/resolve, mcp-registry/io.github.pipeworx-io/mojang/username_to_uuid — capability-matched and ranked by current reliability. mcp-registry/network.tenzro/tenzro/resolve_username itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/roblox/user_by_username	io.github.pipeworx-io/roblox	live status →
mcp-registry/io.github.srotzin/hive-mcp-identity/resolve_did	io.github.srotzin/hive-mcp-identity	live status →
mcp-registry/io.github.farestrabs/agentnet/resolve_identity	io.github.farestrabs/agentnet	live status →
mcp-registry/io.github.majorelalexis-stack/maxia/resolve	io.github.majorelalexis-stack/maxia	live status →
mcp-registry/io.github.pipeworx-io/mojang/username_to_uuid	io.github.pipeworx-io/mojang	live status →
mcp-registry/io.github.pipeworx-io/bluesky/resolve_handle	io.github.pipeworx-io/bluesky	live status →
mcp-registry/io.github.portdeveloper/gulltoppr/resolve_name	io.github.portdeveloper/gulltoppr	live status →
mcp-registry/io.github.pipeworx-io/mojang/username_to_uuid_at	io.github.pipeworx-io/mojang	live status →
mcp-registry/network.tenzro/tenzro-ethereum/eth_resolve_ens	network.tenzro/tenzro-ethereum	live status →
mcp-registry/com.windowsforum/mcp-server/get_user	com.windowsforum/mcp-server	live status →
mcp-registry/io.fuse/mcp/fuse_resolve_ens	io.fuse/mcp	live status →
mcp-registry/io.github.omniologynow-rgb/mcp-server/set_username	io.github.omniologynow-rgb/mcp-server	live status →

FAQ

What is the best alternative to mcp-registry/network.tenzro/tenzro/resolve_username?

mcp-registry/io.github.pipeworx-io/roblox/user_by_username is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.srotzin/hive-mcp-identity/resolve_did, mcp-registry/io.github.farestrabs/agentnet/resolve_identity, mcp-registry/io.github.majorelalexis-stack/maxia/resolve, mcp-registry/io.github.pipeworx-io/mojang/username_to_uuid. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/network.tenzro/tenzro/resolve_username down right now?

mcp-registry/network.tenzro/tenzro/resolve_username's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fnetwork.tenzro%2Ftenzro%2Fresolve_username.

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%2Fnetwork.tenzro%2Ftenzro%2Fresolve_username or MCP find_alternatives. Check mcp-registry/network.tenzro/tenzro/resolve_username's live status: https://glimind.com/tool/mcp-registry/network.tenzro/tenzro/resolve_username.