mcp-registry/cloud.theprotocol/registry/theprotocol_getDisputeById / alternatives

Live alternatives to mcp-registry/cloud.theprotocol/registry/theprotocol_getDisputeById

The best live alternatives to mcp-registry/cloud.theprotocol/registry/theprotocol_getDisputeById right now are mcp-registry/network.tenzro/tenzro/get_dispute, mcp-registry/io.github.lilo-property/mcp-server/get_dispute_evidence_bundle_for_booking, mcp-registry/com.donotact/donotact/donotact_dispute_history_csv, mcp-registry/io.github.korext/governance/get_proof, mcp-registry/io.github.srotzin/hivetrust/hivetrust_file_dispute — capability-matched and ranked by current reliability. mcp-registry/cloud.theprotocol/registry/theprotocol_getDisputeById itself is currently "healthy".

alternative	server
mcp-registry/network.tenzro/tenzro/get_dispute	network.tenzro/tenzro	live status →
mcp-registry/io.github.lilo-property/mcp-server/get_dispute_evidence_bundle_for_booking	io.github.lilo-property/mcp-server	live status →
mcp-registry/com.donotact/donotact/donotact_dispute_history_csv	com.donotact/donotact	live status →
mcp-registry/io.github.korext/governance/get_proof	io.github.Korext/governance	live status →
mcp-registry/io.github.srotzin/hivetrust/hivetrust_file_dispute	io.github.srotzin/hivetrust	live status →
mcp-registry/io.github.dgonlinecode/medibill-saver/list_dispute_scenarios	io.github.DGOnlineCode/medibill-saver	live status →
mcp-registry/com.donotact/donotact/donotact_dispute	com.donotact/donotact	live status →
mcp-registry/com.decision-anchor/da/get_decision	com.decision-anchor/da	live status →
mcp-registry/io.github.szara7678/openakashic/dispute_note	io.github.szara7678/openakashic	live status →
mcp-registry/io.github.dgonlinecode/medibill-saver/get_dispute_scenario	io.github.DGOnlineCode/medibill-saver	live status →

FAQ

What is the best alternative to mcp-registry/cloud.theprotocol/registry/theprotocol_getDisputeById?

mcp-registry/network.tenzro/tenzro/get_dispute is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.lilo-property/mcp-server/get_dispute_evidence_bundle_for_booking, mcp-registry/com.donotact/donotact/donotact_dispute_history_csv, mcp-registry/io.github.korext/governance/get_proof, mcp-registry/io.github.srotzin/hivetrust/hivetrust_file_dispute. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/cloud.theprotocol/registry/theprotocol_getDisputeById down right now?

mcp-registry/cloud.theprotocol/registry/theprotocol_getDisputeById's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcloud.theprotocol%2Fregistry%2Ftheprotocol_getDisputeById.

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%2Fcloud.theprotocol%2Fregistry%2Ftheprotocol_getDisputeById or MCP find_alternatives. Check mcp-registry/cloud.theprotocol/registry/theprotocol_getDisputeById's live status: https://glimind.com/tool/mcp-registry/cloud.theprotocol/registry/theprotocol_getDisputeById.