mcp-registry/io.github.jsonbored/metagraphed/get_chain_calls / alternatives

Live alternatives to mcp-registry/io.github.jsonbored/metagraphed/get_chain_calls

The best live alternatives to mcp-registry/io.github.jsonbored/metagraphed/get_chain_calls right now are mcp-registry/io.github.findimitrov/fintel-discovery/GetOptionsChain, mcp-registry/io.github.pipeworx-io/dbnomics/pipeworx_trending, mcp-registry/io.github.pipeworx-io/clash-royale/pipeworx_trending, mcp-registry/io.github.pipeworx-io/openaq/pipeworx_trending, mcp-registry/io.github.pipeworx-io/census/pipeworx_trending — capability-matched and ranked by current reliability. mcp-registry/io.github.jsonbored/metagraphed/get_chain_calls itself is currently "healthy".

alternative	server
mcp-registry/io.github.findimitrov/fintel-discovery/GetOptionsChain	io.github.findimitrov/fintel-discovery	live status →
mcp-registry/io.github.pipeworx-io/dbnomics/pipeworx_trending	io.github.pipeworx-io/dbnomics	live status →
mcp-registry/io.github.pipeworx-io/clash-royale/pipeworx_trending	io.github.pipeworx-io/clash-royale	live status →
mcp-registry/io.github.pipeworx-io/openaq/pipeworx_trending	io.github.pipeworx-io/openaq	live status →
mcp-registry/io.github.pipeworx-io/census/pipeworx_trending	io.github.pipeworx-io/census	live status →
mcp-registry/io.github.pipeworx-io/ai-feeds/pipeworx_trending	io.github.pipeworx-io/ai-feeds	live status →
mcp-registry/io.github.pipeworx-io/sf-recpark/pipeworx_trending	io.github.pipeworx-io/sf-recpark	live status →
mcp-registry/io.github.pipeworx-io/science-feeds/pipeworx_trending	io.github.pipeworx-io/science-feeds	live status →
mcp-registry/io.github.pipeworx-io/poetrydb/pipeworx_trending	io.github.pipeworx-io/poetrydb	live status →
mcp-registry/io.github.pipeworx-io/gong/pipeworx_trending	io.github.pipeworx-io/gong	live status →
mcp-registry/io.github.pipeworx-io/disney/pipeworx_trending	io.github.pipeworx-io/disney	live status →
mcp-registry/io.github.pipeworx-io/statfin-fi/pipeworx_trending	io.github.pipeworx-io/statfin-fi	live status →

FAQ

What is the best alternative to mcp-registry/io.github.jsonbored/metagraphed/get_chain_calls?

mcp-registry/io.github.findimitrov/fintel-discovery/GetOptionsChain is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/dbnomics/pipeworx_trending, mcp-registry/io.github.pipeworx-io/clash-royale/pipeworx_trending, mcp-registry/io.github.pipeworx-io/openaq/pipeworx_trending, mcp-registry/io.github.pipeworx-io/census/pipeworx_trending. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.jsonbored/metagraphed/get_chain_calls down right now?

mcp-registry/io.github.jsonbored/metagraphed/get_chain_calls's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.jsonbored%2Fmetagraphed%2Fget_chain_calls.

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%2Fio.github.jsonbored%2Fmetagraphed%2Fget_chain_calls or MCP find_alternatives. Check mcp-registry/io.github.jsonbored/metagraphed/get_chain_calls's live status: https://glimind.com/tool/mcp-registry/io.github.jsonbored/metagraphed/get_chain_calls.