mcp-registry/io.github.anchorregistry/ar-mcp/ar_resolve_tree / alternatives

Live alternatives to mcp-registry/io.github.anchorregistry/ar-mcp/ar_resolve_tree

The best live alternatives to mcp-registry/io.github.anchorregistry/ar-mcp/ar_resolve_tree right now are mcp-registry/co.ainumbers/tools/resolve_provenance_ingredient_tree, mcp-registry/io.github.markovianprotocol/provenance/markovian_trace, mcp-registry/io.github.portdeveloper/gulltoppr/resolve_abi, mcp-registry/com.bonissystems/content-provenance/verify_provenance, mcp-registry/io.tooloracle/trustlayer/provenance_trace — capability-matched and ranked by current reliability. mcp-registry/io.github.anchorregistry/ar-mcp/ar_resolve_tree itself is currently "healthy".

alternative	server
mcp-registry/co.ainumbers/tools/resolve_provenance_ingredient_tree	co.ainumbers/tools	live status →
mcp-registry/io.github.markovianprotocol/provenance/markovian_trace	io.github.MarkovianProtocol/provenance	live status →
mcp-registry/io.github.portdeveloper/gulltoppr/resolve_abi	io.github.portdeveloper/gulltoppr	live status →
mcp-registry/com.bonissystems/content-provenance/verify_provenance	com.bonissystems/content-provenance	live status →
mcp-registry/io.tooloracle/trustlayer/provenance_trace	io.tooloracle/trustlayer	live status →
mcp-registry/io.github.ronrey/comos-federation/introspection_system_change_reach	io.github.ronrey/comos-federation	live status →
mcp-registry/io.github.kapoost/humanmcp/read_provenance	io.github.kapoost/humanmcp	live status →
mcp-registry/ai.nullary/nullary/get_finding_provenance	ai.nullary/nullary	live status →
mcp-registry/dev.goldprice/mcp/get_metadata	dev.goldprice/mcp	live status →
mcp-registry/io.github.moonspacenow-tech/aicomglobal/aicom_get_proof	io.github.moonspacenow-tech/aicomglobal	live status →
mcp-registry/io.github.kapoost/humanmcp/list_provenance	io.github.kapoost/humanmcp	live status →
mcp-registry/io.github.smq9sn5jck-coder/causallayer/get_anchor_status	io.github.smq9sn5jck-coder/causallayer	live status →

FAQ

What is the best alternative to mcp-registry/io.github.anchorregistry/ar-mcp/ar_resolve_tree?

mcp-registry/co.ainumbers/tools/resolve_provenance_ingredient_tree is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.markovianprotocol/provenance/markovian_trace, mcp-registry/io.github.portdeveloper/gulltoppr/resolve_abi, mcp-registry/com.bonissystems/content-provenance/verify_provenance, mcp-registry/io.tooloracle/trustlayer/provenance_trace. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.anchorregistry/ar-mcp/ar_resolve_tree down right now?

mcp-registry/io.github.anchorregistry/ar-mcp/ar_resolve_tree's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.anchorregistry%2Far-mcp%2Far_resolve_tree.

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.anchorregistry%2Far-mcp%2Far_resolve_tree or MCP find_alternatives. Check mcp-registry/io.github.anchorregistry/ar-mcp/ar_resolve_tree's live status: https://glimind.com/tool/mcp-registry/io.github.anchorregistry/ar-mcp/ar_resolve_tree.