mcp-registry/dev.metamesh-uga/metamesh-uga/metamesh.metrics / alternatives

Live alternatives to mcp-registry/dev.metamesh-uga/metamesh-uga/metamesh.metrics

The best live alternatives to mcp-registry/dev.metamesh-uga/metamesh-uga/metamesh.metrics right now are mcp-registry/io.github.shawndei/glimind/list_breakages, mcp-registry/io.github.pipeworx-io/openverse/pipeworx_trending, mcp-registry/io.github.pipeworx-io/data-ny/pipeworx_trending, mcp-registry/io.github.pipeworx-io/data-nashville/pipeworx_trending, mcp-registry/io.github.pipeworx-io/data-michigan/pipeworx_trending — capability-matched and ranked by current reliability. mcp-registry/dev.metamesh-uga/metamesh-uga/metamesh.metrics itself is currently "healthy".

alternative	server
mcp-registry/io.github.shawndei/glimind/list_breakages	io.github.shawndei/glimind	live status →
mcp-registry/io.github.pipeworx-io/openverse/pipeworx_trending	io.github.pipeworx-io/openverse	live status →
mcp-registry/io.github.pipeworx-io/data-ny/pipeworx_trending	io.github.pipeworx-io/data-ny	live status →
mcp-registry/io.github.pipeworx-io/data-nashville/pipeworx_trending	io.github.pipeworx-io/data-nashville	live status →
mcp-registry/io.github.pipeworx-io/data-michigan/pipeworx_trending	io.github.pipeworx-io/data-michigan	live status →
mcp-registry/io.github.pipeworx-io/data-mesa/pipeworx_trending	io.github.pipeworx-io/data-mesa	live status →
mcp-registry/io.github.pipeworx-io/data-maryland/pipeworx_trending	io.github.pipeworx-io/data-maryland	live status →
mcp-registry/io.github.pipeworx-io/data-kingcounty/pipeworx_trending	io.github.pipeworx-io/data-kingcounty	live status →
mcp-registry/io.github.pipeworx-io/data-fcc/pipeworx_trending	io.github.pipeworx-io/data-fcc	live status →
mcp-registry/io.github.pipeworx-io/data-energystar/pipeworx_trending	io.github.pipeworx-io/data-energystar	live status →
mcp-registry/io.github.pipeworx-io/spoonacular/pipeworx_trending	io.github.pipeworx-io/spoonacular	live status →
mcp-registry/io.github.pipeworx-io/snb-ch/pipeworx_trending	io.github.pipeworx-io/snb-ch	live status →

FAQ

What is the best alternative to mcp-registry/dev.metamesh-uga/metamesh-uga/metamesh.metrics?

mcp-registry/io.github.shawndei/glimind/list_breakages is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/openverse/pipeworx_trending, mcp-registry/io.github.pipeworx-io/data-ny/pipeworx_trending, mcp-registry/io.github.pipeworx-io/data-nashville/pipeworx_trending, mcp-registry/io.github.pipeworx-io/data-michigan/pipeworx_trending. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/dev.metamesh-uga/metamesh-uga/metamesh.metrics down right now?

mcp-registry/dev.metamesh-uga/metamesh-uga/metamesh.metrics's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fdev.metamesh-uga%2Fmetamesh-uga%2Fmetamesh.metrics.

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%2Fdev.metamesh-uga%2Fmetamesh-uga%2Fmetamesh.metrics or MCP find_alternatives. Check mcp-registry/dev.metamesh-uga/metamesh-uga/metamesh.metrics's live status: https://glimind.com/tool/mcp-registry/dev.metamesh-uga/metamesh-uga/metamesh.metrics.