mcp-registry/com.progenly/progenly/merge_status / alternatives

Live alternatives to mcp-registry/com.progenly/progenly/merge_status

The best live alternatives to mcp-registry/com.progenly/progenly/merge_status right now are mcp-registry/io.github.ajc3xc/meridian/add_subtask, mcp-registry/io.github.rationalbloks/rationalbloks-mcp/deploy_staging, mcp-registry/io.github.causehacker/quicksign/get_draft_status, mcp-registry/space.0/space0/update_commitment, mcp-registry/be.vibedeploy/vibedeploy/list_deploys — capability-matched and ranked by current reliability. mcp-registry/com.progenly/progenly/merge_status itself is currently "healthy".

alternative	server
mcp-registry/io.github.ajc3xc/meridian/add_subtask	io.github.ajc3xc/meridian	live status →
mcp-registry/io.github.rationalbloks/rationalbloks-mcp/deploy_staging	io.github.rationalbloks/rationalbloks-mcp	live status →
mcp-registry/io.github.causehacker/quicksign/get_draft_status	io.github.causehacker/quicksign	live status →
mcp-registry/space.0/space0/update_commitment	space.0/space0	live status →
mcp-registry/be.vibedeploy/vibedeploy/list_deploys	be.vibedeploy/vibedeploy	live status →
mcp-registry/xyz.signomy/civitae/admin.stakes	xyz.signomy/civitae	live status →
mcp-registry/io.github.a0985344368-glitch/tsung-ai/ghost_status	io.github.a0985344368-glitch/tsung-ai	live status →
mcp-registry/cz.salesbot/linkedin-mcp-server/set_deal_stage	cz.salesbot/linkedin-mcp-server	live status →
mcp-registry/io.github.planexeorg/planexe/plan_status	io.github.PlanExeOrg/planexe	live status →
mcp-registry/io.github.megachadxyz/megachad/build_staking_tx	io.github.megachadxyz/megachad	live status →
mcp-registry/io.sota/mcp/get-status	io.sota/mcp	live status →
mcp-registry/io.github.rationalbloks/rationalbloks-mcp/deploy_graph_staging	io.github.rationalbloks/rationalbloks-mcp	live status →

FAQ

What is the best alternative to mcp-registry/com.progenly/progenly/merge_status?

mcp-registry/io.github.ajc3xc/meridian/add_subtask is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.rationalbloks/rationalbloks-mcp/deploy_staging, mcp-registry/io.github.causehacker/quicksign/get_draft_status, mcp-registry/space.0/space0/update_commitment, mcp-registry/be.vibedeploy/vibedeploy/list_deploys. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.progenly/progenly/merge_status down right now?

mcp-registry/com.progenly/progenly/merge_status's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.progenly%2Fprogenly%2Fmerge_status.

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.progenly%2Fprogenly%2Fmerge_status or MCP find_alternatives. Check mcp-registry/com.progenly/progenly/merge_status's live status: https://glimind.com/tool/mcp-registry/com.progenly/progenly/merge_status.