mcp-registry/io.github.pipeworx-io/mojang/name_history / alternatives
mcp-registry/io.github.pipeworx-io/mojang/name_historyThe best live alternatives to mcp-registry/io.github.pipeworx-io/mojang/name_history right now are mcp-registry/io.github.cammac-creator/openswissdata/entity_history, mcp-registry/io.github.alexeibespalov/trident/get_recent_changes, mcp-registry/io.github.pipeworx-io/datos-cl/recent_changes, mcp-registry/io.github.pipeworx-io/n2yo/recent_changes, mcp-registry/io.github.pipeworx-io/montreal-events/recent_changes — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/mojang/name_history itself is currently "healthy".
mcp-registry/io.github.cammac-creator/openswissdata/entity_history is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.alexeibespalov/trident/get_recent_changes, mcp-registry/io.github.pipeworx-io/datos-cl/recent_changes, mcp-registry/io.github.pipeworx-io/n2yo/recent_changes, mcp-registry/io.github.pipeworx-io/montreal-events/recent_changes. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.pipeworx-io/mojang/name_history's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fmojang%2Fname_history.
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.pipeworx-io%2Fmojang%2Fname_history
or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/mojang/name_history's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/mojang/name_history.