mcp-registry/io.github.anchorregistry/ar-mcp/ar_verify_by_hash / alternatives
mcp-registry/io.github.anchorregistry/ar-mcp/ar_verify_by_hashThe best live alternatives to mcp-registry/io.github.anchorregistry/ar-mcp/ar_verify_by_hash right now are mcp-registry/com.bonissystems/content-provenance/verify_provenance, mcp-registry/co.ainumbers/tools/verify_execution_hash, mcp-registry/com.verisgov.api/data-access/verify_seal, mcp-registry/io.github.getambr/ambr-mcp-server/ambr_verify_hash, mcp-registry/com.dropwatchhq/compliance-evidence/verify_pack — capability-matched and ranked by current reliability. mcp-registry/io.github.anchorregistry/ar-mcp/ar_verify_by_hash itself is currently "healthy".
mcp-registry/com.bonissystems/content-provenance/verify_provenance is the top capability-matched alternative that's live right now. Other options: mcp-registry/co.ainumbers/tools/verify_execution_hash, mcp-registry/com.verisgov.api/data-access/verify_seal, mcp-registry/io.github.getambr/ambr-mcp-server/ambr_verify_hash, mcp-registry/com.dropwatchhq/compliance-evidence/verify_pack. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.anchorregistry/ar-mcp/ar_verify_by_hash's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.anchorregistry%2Far-mcp%2Far_verify_by_hash.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.anchorregistry%2Far-mcp%2Far_verify_by_hash
or MCP find_alternatives. Check mcp-registry/io.github.anchorregistry/ar-mcp/ar_verify_by_hash's live status: https://glimind.com/tool/mcp-registry/io.github.anchorregistry/ar-mcp/ar_verify_by_hash.