mcp-registry/ai.tunnelmind/scry/scry_recent / alternatives

Live alternatives to mcp-registry/ai.tunnelmind/scry/scry_recent

The best live alternatives to mcp-registry/ai.tunnelmind/scry/scry_recent right now are mcp-registry/it.elsas/security-intel/get_since, mcp-registry/io.github.pipeworx-io/uniprot/recent_changes, mcp-registry/io.github.pipeworx-io/nuget/recent_changes, mcp-registry/io.github.pipeworx-io/launch-library/recent_changes, mcp-registry/io.github.pipeworx-io/trove/recent_changes — capability-matched and ranked by current reliability. mcp-registry/ai.tunnelmind/scry/scry_recent itself is currently "healthy".

alternative	server
mcp-registry/it.elsas/security-intel/get_since	it.elsas/security-intel	live status →
mcp-registry/io.github.pipeworx-io/uniprot/recent_changes	io.github.pipeworx-io/uniprot	live status →
mcp-registry/io.github.pipeworx-io/nuget/recent_changes	io.github.pipeworx-io/nuget	live status →
mcp-registry/io.github.pipeworx-io/launch-library/recent_changes	io.github.pipeworx-io/launch-library	live status →
mcp-registry/io.github.pipeworx-io/trove/recent_changes	io.github.pipeworx-io/trove	live status →
mcp-registry/io.github.pipeworx-io/crypto/recent_changes	io.github.pipeworx-io/crypto	live status →
mcp-registry/io.github.pipeworx-io/data-cincinnati/recent_changes	io.github.pipeworx-io/data-cincinnati	live status →
mcp-registry/io.github.pipeworx-io/data-centrevaldeloire/recent_changes	io.github.pipeworx-io/data-centrevaldeloire	live status →
mcp-registry/io.github.pipeworx-io/usda-fdc/recent_changes	io.github.pipeworx-io/usda-fdc	live status →
mcp-registry/io.github.pipeworx-io/chargebee/recent_changes	io.github.pipeworx-io/chargebee	live status →
mcp-registry/io.github.pipeworx-io/oqmd/recent_changes	io.github.pipeworx-io/oqmd	live status →
mcp-registry/io.github.pipeworx-io/data-delaware/recent_changes	io.github.pipeworx-io/data-delaware	live status →

FAQ

What is the best alternative to mcp-registry/ai.tunnelmind/scry/scry_recent?

mcp-registry/it.elsas/security-intel/get_since is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/uniprot/recent_changes, mcp-registry/io.github.pipeworx-io/nuget/recent_changes, mcp-registry/io.github.pipeworx-io/launch-library/recent_changes, mcp-registry/io.github.pipeworx-io/trove/recent_changes. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/ai.tunnelmind/scry/scry_recent down right now?

mcp-registry/ai.tunnelmind/scry/scry_recent's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fai.tunnelmind%2Fscry%2Fscry_recent.

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%2Fai.tunnelmind%2Fscry%2Fscry_recent or MCP find_alternatives. Check mcp-registry/ai.tunnelmind/scry/scry_recent's live status: https://glimind.com/tool/mcp-registry/ai.tunnelmind/scry/scry_recent.