mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/set_published_tier / alternatives

Live alternatives to mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/set_published_tier

The best live alternatives to mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/set_published_tier right now are mcp-registry/cloud.theprotocol/registry/theprotocol_getStakingApyTiersTeg, mcp-registry/io.github.szara7678/openakashic/set_note_publication_status, mcp-registry/io.github.ivaavimusic/singularity/update_endpoint, pulsemcp/adbutler/update_publisher, mcp-registry/com.adbutler/mcp-server/update_publisher — capability-matched and ranked by current reliability. mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/set_published_tier itself is currently "healthy".

alternative	server
mcp-registry/cloud.theprotocol/registry/theprotocol_getStakingApyTiersTeg	cloud.theprotocol/registry	live status →
mcp-registry/io.github.szara7678/openakashic/set_note_publication_status	io.github.szara7678/openakashic	live status →
mcp-registry/io.github.ivaavimusic/singularity/update_endpoint	io.github.ivaavimusic/singularity	live status →
pulsemcp/adbutler/update_publisher	AdButler	live status →
mcp-registry/com.adbutler/mcp-server/update_publisher	com.adbutler/mcp-server	live status →
mcp-registry/io.github.makeev/alphai-mcp/alphai_alerts_subscribe	io.github.makeev/alphai-mcp	live status →
mcp-registry/io.stablebaseline/sb/getPriceForTier	io.stablebaseline/sb	live status →
mcp-registry/io.github.parallect/prxhub/set_metadata	io.github.parallect/prxhub	live status →
mcp-registry/io.github.makeev/alphai-mcp/alphai_actionable_now	io.github.makeev/alphai-mcp	live status →
mcp-registry/ai.agentberg/agentberg/publish_finding	ai.agentberg/agentberg	live status →
mcp-registry/ai.agentberg/agentberg/query_findings	ai.agentberg/agentberg	live status →
mcp-registry/io.github.stevemilton/marketplace/update_commitment_status	io.github.stevemilton/marketplace	live status →

FAQ

What is the best alternative to mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/set_published_tier?

mcp-registry/cloud.theprotocol/registry/theprotocol_getStakingApyTiersTeg is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.szara7678/openakashic/set_note_publication_status, mcp-registry/io.github.ivaavimusic/singularity/update_endpoint, pulsemcp/adbutler/update_publisher, mcp-registry/com.adbutler/mcp-server/update_publisher. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/set_published_tier down right now?

mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/set_published_tier's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.capratesignals-cpu%2Fcap-rate-signals%2Fset_published_tier.

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.capratesignals-cpu%2Fcap-rate-signals%2Fset_published_tier or MCP find_alternatives. Check mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/set_published_tier's live status: https://glimind.com/tool/mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/set_published_tier.