mcp-registry/io.github.localgov-jp/mcp-server/subscribe_changes / alternatives

Live alternatives to mcp-registry/io.github.localgov-jp/mcp-server/subscribe_changes

The best live alternatives to mcp-registry/io.github.localgov-jp/mcp-server/subscribe_changes right now are mcp-registry/io.github.mirabello-consultancy/mcp-server/subscribe_changes, mcp-registry/ai.licensy/mcp-server/subscribe_to_changes, mcp-registry/io.911fund.x402/x402-alpha/alpha_subscribe, mcp-registry/com.dropwatchhq/ai-api-radar/price_change_alerts, mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/freshness_subscribe — capability-matched and ranked by current reliability. mcp-registry/io.github.localgov-jp/mcp-server/subscribe_changes itself is currently "healthy".

alternative	server
mcp-registry/io.github.mirabello-consultancy/mcp-server/subscribe_changes	io.github.mirabello-consultancy/mcp-server	live status →
mcp-registry/ai.licensy/mcp-server/subscribe_to_changes	ai.licensy/mcp-server	live status →
mcp-registry/io.911fund.x402/x402-alpha/alpha_subscribe	io.911fund.x402/x402-alpha	live status →
mcp-registry/com.dropwatchhq/ai-api-radar/price_change_alerts	com.dropwatchhq/ai-api-radar	live status →
mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/freshness_subscribe	com.mcp-revenue-empire/japan-public-ledgers	live status →
mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_webhook_create	com.mcp-revenue-empire/japan-public-ledgers	live status →
mcp-registry/io.github.xbt786/hipaa-agent/subscribe_webhook	io.github.xbt786/hipaa-agent	live status →
mcp-registry/ai.licensy/mcp-server/unsubscribe	ai.licensy/mcp-server	live status →
mcp-registry/io.github.lazymac2x/api-changelog-tracker/subscribe_feed	io.github.lazymac2x/api-changelog-tracker	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_agent_approval_workflow_compiler	xyz.558686.gpt55/token-gateway	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_agent_core_integration_kit_get	xyz.558686.gpt55/token-gateway	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_agent_core_integration_kit	xyz.558686.gpt55/token-gateway	live status →

FAQ

What is the best alternative to mcp-registry/io.github.localgov-jp/mcp-server/subscribe_changes?

mcp-registry/io.github.mirabello-consultancy/mcp-server/subscribe_changes is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.licensy/mcp-server/subscribe_to_changes, mcp-registry/io.911fund.x402/x402-alpha/alpha_subscribe, mcp-registry/com.dropwatchhq/ai-api-radar/price_change_alerts, mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/freshness_subscribe. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.localgov-jp/mcp-server/subscribe_changes down right now?

mcp-registry/io.github.localgov-jp/mcp-server/subscribe_changes's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.localgov-jp%2Fmcp-server%2Fsubscribe_changes.

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.localgov-jp%2Fmcp-server%2Fsubscribe_changes or MCP find_alternatives. Check mcp-registry/io.github.localgov-jp/mcp-server/subscribe_changes's live status: https://glimind.com/tool/mcp-registry/io.github.localgov-jp/mcp-server/subscribe_changes.