mcp-registry/org.duckdns.cryptogenesis/safe-agent/trending / alternatives

Live alternatives to mcp-registry/org.duckdns.cryptogenesis/safe-agent/trending

The best live alternatives to mcp-registry/org.duckdns.cryptogenesis/safe-agent/trending right now are mcp-registry/io.github.0580iris-lang/x711-gas-station/x711_hive_trending, pulsemcp/x711/x711_hive_trending, mcp-registry/io.github.pipeworx-io/fbiwanted/pipeworx_trending, mcp-registry/io.github.pipeworx-io/sec-xbrl/pipeworx_trending, mcp-registry/io.github.pipeworx-io/sunrisesunset/pipeworx_trending — capability-matched and ranked by current reliability. mcp-registry/org.duckdns.cryptogenesis/safe-agent/trending itself is currently "healthy".

alternative	server
mcp-registry/io.github.0580iris-lang/x711-gas-station/x711_hive_trending	io.github.0580iris-lang/x711-gas-station	live status →
pulsemcp/x711/x711_hive_trending	x711	live status →
mcp-registry/io.github.pipeworx-io/fbiwanted/pipeworx_trending	io.github.pipeworx-io/fbiwanted	live status →
mcp-registry/io.github.pipeworx-io/sec-xbrl/pipeworx_trending	io.github.pipeworx-io/sec-xbrl	live status →
mcp-registry/io.github.pipeworx-io/sunrisesunset/pipeworx_trending	io.github.pipeworx-io/sunrisesunset	live status →
mcp-registry/io.github.pipeworx-io/arcgis-allegheny/pipeworx_trending	io.github.pipeworx-io/arcgis-allegheny	live status →
mcp-registry/io.github.pipeworx-io/arcgis-greenwood/pipeworx_trending	io.github.pipeworx-io/arcgis-greenwood	live status →
mcp-registry/io.github.pipeworx-io/l2beat/pipeworx_trending	io.github.pipeworx-io/l2beat	live status →
mcp-registry/io.github.pipeworx-io/prayer-times/pipeworx_trending	io.github.pipeworx-io/prayer-times	live status →
mcp-registry/io.github.pipeworx-io/onthisday/pipeworx_trending	io.github.pipeworx-io/onthisday	live status →
mcp-registry/io.github.pipeworx-io/transport-feeds/pipeworx_trending	io.github.pipeworx-io/transport-feeds	live status →
mcp-registry/io.github.pipeworx-io/schemastore/pipeworx_trending	io.github.pipeworx-io/schemastore	live status →

FAQ

What is the best alternative to mcp-registry/org.duckdns.cryptogenesis/safe-agent/trending?

mcp-registry/io.github.0580iris-lang/x711-gas-station/x711_hive_trending is the top capability-matched alternative that's live right now. Other options: pulsemcp/x711/x711_hive_trending, mcp-registry/io.github.pipeworx-io/fbiwanted/pipeworx_trending, mcp-registry/io.github.pipeworx-io/sec-xbrl/pipeworx_trending, mcp-registry/io.github.pipeworx-io/sunrisesunset/pipeworx_trending. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/org.duckdns.cryptogenesis/safe-agent/trending down right now?

mcp-registry/org.duckdns.cryptogenesis/safe-agent/trending's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Forg.duckdns.cryptogenesis%2Fsafe-agent%2Ftrending.

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%2Forg.duckdns.cryptogenesis%2Fsafe-agent%2Ftrending or MCP find_alternatives. Check mcp-registry/org.duckdns.cryptogenesis/safe-agent/trending's live status: https://glimind.com/tool/mcp-registry/org.duckdns.cryptogenesis/safe-agent/trending.