mcp-registry/com.blockscout/mcp-server/direct_api_call / alternatives

Live alternatives to mcp-registry/com.blockscout/mcp-server/direct_api_call

The best live alternatives to mcp-registry/com.blockscout/mcp-server/direct_api_call right now are mcp-registry/com.adbutler/mcp-server/call_adbutler_api, pulsemcp/adbutler/call_adbutler_api, mcp-registry/io.github.vybenetwork/vybe-solana-api/search-endpoints, mcp-registry/io.github.branch-docs/ai/search-endpoints, mcp-registry/com.adbutler/mcp-server/search_adbutler_api — capability-matched and ranked by current reliability. mcp-registry/com.blockscout/mcp-server/direct_api_call itself is currently "healthy".

alternative	server
mcp-registry/com.adbutler/mcp-server/call_adbutler_api	com.adbutler/mcp-server	live status →
pulsemcp/adbutler/call_adbutler_api	AdButler	live status →
mcp-registry/io.github.vybenetwork/vybe-solana-api/search-endpoints	io.github.vybenetwork/vybe-solana-api	live status →
mcp-registry/io.github.branch-docs/ai/search-endpoints	io.github.branch-docs/ai	live status →
mcp-registry/com.adbutler/mcp-server/search_adbutler_api	com.adbutler/mcp-server	live status →
pulsemcp/adbutler/search_adbutler_api	AdButler	live status →
mcp-registry/ai.proxygate/mcp/call_api	ai.proxygate/mcp	live status →
mcp-registry/io.github.snehdhruv/trillboards-dooh/describe_endpoint	io.github.snehdhruv/trillboards-dooh	live status →
mcp-registry/io.github.saloprj/dialogbrain/workbench_run_python	io.github.saloprj/dialogbrain	live status →
mcp-registry/ai.proxygate/mcp/describe_endpoint	ai.proxygate/mcp	live status →
mcp-registry/io.github.jsonbored/metagraphed/list_blocks	io.github.JSONbored/metagraphed	live status →
mcp-registry/com.adbutler/mcp-server/describe_adbutler_api	com.adbutler/mcp-server	live status →

FAQ

What is the best alternative to mcp-registry/com.blockscout/mcp-server/direct_api_call?

mcp-registry/com.adbutler/mcp-server/call_adbutler_api is the top capability-matched alternative that's live right now. Other options: pulsemcp/adbutler/call_adbutler_api, mcp-registry/io.github.vybenetwork/vybe-solana-api/search-endpoints, mcp-registry/io.github.branch-docs/ai/search-endpoints, mcp-registry/com.adbutler/mcp-server/search_adbutler_api. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.blockscout/mcp-server/direct_api_call down right now?

mcp-registry/com.blockscout/mcp-server/direct_api_call's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.blockscout%2Fmcp-server%2Fdirect_api_call.

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%2Fcom.blockscout%2Fmcp-server%2Fdirect_api_call or MCP find_alternatives. Check mcp-registry/com.blockscout/mcp-server/direct_api_call's live status: https://glimind.com/tool/mcp-registry/com.blockscout/mcp-server/direct_api_call.