mcp-registry/io.github.hslee16/archy/score_record / alternatives

Live alternatives to mcp-registry/io.github.hslee16/archy/score_record

The best live alternatives to mcp-registry/io.github.hslee16/archy/score_record right now are mcp-registry/io.tooloracle/ampel/score_trend, mcp-registry/io.tooloracle/predictoracle/predict_score, mcp-registry/io.github.johanvd75-byte/cracks-index/score_trends, mcp-registry/io.tooloracle/predictoracle/trend_analysis, mcp-registry/app.saber.mcp/saber/scoring-compute — capability-matched and ranked by current reliability. mcp-registry/io.github.hslee16/archy/score_record itself is currently "unknown".

alternative	server
mcp-registry/io.tooloracle/ampel/score_trend	io.tooloracle/ampel	live status →
mcp-registry/io.tooloracle/predictoracle/predict_score	io.tooloracle/predictoracle	live status →
mcp-registry/io.github.johanvd75-byte/cracks-index/score_trends	io.github.johanvd75-byte/cracks-index	live status →
mcp-registry/io.tooloracle/predictoracle/trend_analysis	io.tooloracle/predictoracle	live status →
mcp-registry/app.saber.mcp/saber/scoring-compute	app.saber.mcp/saber	live status →
mcp-registry/io.github.bch1212/bizintel/score_lead	io.github.bch1212/bizintel	live status →
mcp-registry/io.github.baneado98/freight-pulse/get_scorecard	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.goatgaucho/trustlayer/get_score_history	io.github.goatgaucho/trustlayer	live status →
mcp-registry/io.sentinelsignal/scoring/score_workflow	io.sentinelsignal/scoring	live status →
mcp-registry/io.apis/apis-io/find_ratings	io.apis/apis-io	live status →
mcp-registry/app.saber.mcp/saber/scoring-profile-update	app.saber.mcp/saber	live status →

FAQ

What is the best alternative to mcp-registry/io.github.hslee16/archy/score_record?

mcp-registry/io.tooloracle/ampel/score_trend is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.tooloracle/predictoracle/predict_score, mcp-registry/io.github.johanvd75-byte/cracks-index/score_trends, mcp-registry/io.tooloracle/predictoracle/trend_analysis, mcp-registry/app.saber.mcp/saber/scoring-compute. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.hslee16/archy/score_record down right now?

mcp-registry/io.github.hslee16/archy/score_record's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.hslee16%2Farchy%2Fscore_record.

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.hslee16%2Farchy%2Fscore_record or MCP find_alternatives. Check mcp-registry/io.github.hslee16/archy/score_record's live status: https://glimind.com/tool/mcp-registry/io.github.hslee16/archy/score_record.