mcp-registry/ai.proxygate/mcp/call_api / alternatives

Live alternatives to mcp-registry/ai.proxygate/mcp/call_api

The best live alternatives to mcp-registry/ai.proxygate/mcp/call_api right now are mcp-registry/io.github.obcraft/apiosk-mcp/apiosk_payment_guide, mcp-registry/io.github.srotzin/hivegate/hivegate_execute, mcp-registry/io.github.apihubio/mcp-server/apihub_call, mcp-registry/xyz.actiongate.api/actiongate/policy_gate, pulsemcp/actiongate/policy_gate — capability-matched and ranked by current reliability. mcp-registry/ai.proxygate/mcp/call_api itself is currently "healthy".

alternative	server
mcp-registry/io.github.obcraft/apiosk-mcp/apiosk_payment_guide	io.github.obcraft/apiosk-mcp	live status →
mcp-registry/io.github.srotzin/hivegate/hivegate_execute	io.github.srotzin/hivegate	live status →
mcp-registry/io.github.apihubio/mcp-server/apihub_call	io.github.apihubio/mcp-server	live status →
mcp-registry/xyz.actiongate.api/actiongate/policy_gate	xyz.actiongate.api/actiongate	live status →
pulsemcp/actiongate/policy_gate	ActionGate	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_batch_quote_inspector_get	xyz.558686.gpt55/token-gateway	live status →
mcp-registry/io.github.apihubio/mcp-server/apihub_call_external	io.github.apihubio/mcp-server	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_private_gateway_deployment_plan	xyz.558686.gpt55/token-gateway	live status →
mcp-registry/io.apis/apis-io/get_api	io.apis/apis-io	live status →
mcp-registry/com.wingmanprotocol.agent/gateway/vault_call_api	com.wingmanprotocol.agent/gateway	live status →
mcp-registry/ai.sugra/api-mcp/call_endpoint	ai.sugra/api-mcp	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_batch_quote_inspector	xyz.558686.gpt55/token-gateway	live status →

FAQ

What is the best alternative to mcp-registry/ai.proxygate/mcp/call_api?

mcp-registry/io.github.obcraft/apiosk-mcp/apiosk_payment_guide is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.srotzin/hivegate/hivegate_execute, mcp-registry/io.github.apihubio/mcp-server/apihub_call, mcp-registry/xyz.actiongate.api/actiongate/policy_gate, pulsemcp/actiongate/policy_gate. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/ai.proxygate/mcp/call_api down right now?

mcp-registry/ai.proxygate/mcp/call_api's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fai.proxygate%2Fmcp%2Fcall_api.

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%2Fai.proxygate%2Fmcp%2Fcall_api or MCP find_alternatives. Check mcp-registry/ai.proxygate/mcp/call_api's live status: https://glimind.com/tool/mcp-registry/ai.proxygate/mcp/call_api.