mcp-registry/ai.boolsai/signals/scan_at_date / alternatives

Live alternatives to mcp-registry/ai.boolsai/signals/scan_at_date

The best live alternatives to mcp-registry/ai.boolsai/signals/scan_at_date right now are mcp-registry/io.github.pipeworx-io/wayback/get_snapshot, mcp-registry/ai.tunnelmind/scry/scry_recent, mcp-registry/it.elsas/security-intel/get_since, mcp-registry/io.github.tathagat22/slipstream/whats_new, mcp-registry/io.github.pipeworx-io/nuget/recent_changes — capability-matched and ranked by current reliability. mcp-registry/ai.boolsai/signals/scan_at_date itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/wayback/get_snapshot	io.github.pipeworx-io/wayback	live status →
mcp-registry/ai.tunnelmind/scry/scry_recent	ai.tunnelmind/scry	live status →
mcp-registry/it.elsas/security-intel/get_since	it.elsas/security-intel	live status →
mcp-registry/io.github.tathagat22/slipstream/whats_new	io.github.tathagat22/slipstream	live status →
mcp-registry/io.github.pipeworx-io/nuget/recent_changes	io.github.pipeworx-io/nuget	live status →
mcp-registry/io.github.pipeworx-io/uniprot/recent_changes	io.github.pipeworx-io/uniprot	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/currents/recent_changes	io.github.pipeworx-io/currents	live status →
mcp-registry/io.github.pipeworx-io/crates/recent_changes	io.github.pipeworx-io/crates	live status →
mcp-registry/io.github.pipeworx-io/data-delaware/recent_changes	io.github.pipeworx-io/data-delaware	live status →
mcp-registry/io.github.pipeworx-io/oqmd/recent_changes	io.github.pipeworx-io/oqmd	live status →

FAQ

What is the best alternative to mcp-registry/ai.boolsai/signals/scan_at_date?

mcp-registry/io.github.pipeworx-io/wayback/get_snapshot is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.tunnelmind/scry/scry_recent, mcp-registry/it.elsas/security-intel/get_since, mcp-registry/io.github.tathagat22/slipstream/whats_new, mcp-registry/io.github.pipeworx-io/nuget/recent_changes. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/ai.boolsai/signals/scan_at_date down right now?

mcp-registry/ai.boolsai/signals/scan_at_date's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fai.boolsai%2Fsignals%2Fscan_at_date.

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.boolsai%2Fsignals%2Fscan_at_date or MCP find_alternatives. Check mcp-registry/ai.boolsai/signals/scan_at_date's live status: https://glimind.com/tool/mcp-registry/ai.boolsai/signals/scan_at_date.