mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_proxy_fetch / alternatives

Live alternatives to mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_proxy_fetch

The best live alternatives to mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_proxy_fetch right now are mcp-registry/com.contrastcyber/api/robots_txt, mcp-registry/ai.intuitek.the-stall/the-stall/agent-access-check, mcp-registry/dev.charliemorrison/agent-web-reader/agent_web_reader, mcp-registry/io.github.pipeworx-io/httpbin/robots_txt, mcp-registry/ai.proxygate/mcp/browse_apis — capability-matched and ranked by current reliability. mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_proxy_fetch itself is currently "healthy".

alternative	server
mcp-registry/com.contrastcyber/api/robots_txt	com.contrastcyber/api	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/agent-access-check	ai.intuitek.the-stall/the-stall	live status →
mcp-registry/dev.charliemorrison/agent-web-reader/agent_web_reader	dev.charliemorrison/agent-web-reader	live status →
mcp-registry/io.github.pipeworx-io/httpbin/robots_txt	io.github.pipeworx-io/httpbin	live status →
mcp-registry/ai.proxygate/mcp/browse_apis	ai.proxygate/mcp	live status →
mcp-registry/io.github.rccola990-cloud/x402-agent-store/api_generate	io.github.rccola990-cloud/x402-agent-store	live status →
mcp-registry/ai.sitepulsar/mcp/check_agent_readiness	ai.sitepulsar/mcp	live status →
mcp-registry/io.github.pipeworx-io/crypto-feeds/fetch_feed	io.github.pipeworx-io/crypto-feeds	live status →
mcp-registry/io.github.pipeworx-io/climate-feeds/fetch_feed	io.github.pipeworx-io/climate-feeds	live status →
mcp-registry/io.github.pipeworx-io/entertainment-feeds/fetch_feed	io.github.pipeworx-io/entertainment-feeds	live status →
mcp-registry/io.github.pipeworx-io/transport-feeds/fetch_feed	io.github.pipeworx-io/transport-feeds	live status →
mcp-registry/io.github.pipeworx-io/travel-feeds/fetch_feed	io.github.pipeworx-io/travel-feeds	live status →

FAQ

What is the best alternative to mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_proxy_fetch?

mcp-registry/com.contrastcyber/api/robots_txt is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.intuitek.the-stall/the-stall/agent-access-check, mcp-registry/dev.charliemorrison/agent-web-reader/agent_web_reader, mcp-registry/io.github.pipeworx-io/httpbin/robots_txt, mcp-registry/ai.proxygate/mcp/browse_apis. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_proxy_fetch down right now?

mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_proxy_fetch's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.mcp-revenue-empire%2Fjapan-public-ledgers%2Fagent_proxy_fetch.

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%2Fcom.mcp-revenue-empire%2Fjapan-public-ledgers%2Fagent_proxy_fetch or MCP find_alternatives. Check mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_proxy_fetch's live status: https://glimind.com/tool/mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_proxy_fetch.