mcp-registry/io.github.nexus-api-lab/chrono-mcp/duration_between / alternatives
mcp-registry/io.github.nexus-api-lab/chrono-mcp/duration_betweenThe best live alternatives to mcp-registry/io.github.nexus-api-lab/chrono-mcp/duration_between right now are mcp-registry/io.tinyfn/tinyfn/time_difference, mcp-registry/io.tinyfn/tinyfn/date_diff, mcp-registry/io.tinyfn/tinyfn/business_days, mcp-registry/io.tinyfn/tinyfn/subtract_time, mcp-registry/io.github.foundrynet/foundrynet-geo/distance — capability-matched and ranked by current reliability. mcp-registry/io.github.nexus-api-lab/chrono-mcp/duration_between itself is currently "healthy".
mcp-registry/io.tinyfn/tinyfn/time_difference is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.tinyfn/tinyfn/date_diff, mcp-registry/io.tinyfn/tinyfn/business_days, mcp-registry/io.tinyfn/tinyfn/subtract_time, mcp-registry/io.github.foundrynet/foundrynet-geo/distance. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.nexus-api-lab/chrono-mcp/duration_between's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.nexus-api-lab%2Fchrono-mcp%2Fduration_between.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.nexus-api-lab%2Fchrono-mcp%2Fduration_between
or MCP find_alternatives. Check mcp-registry/io.github.nexus-api-lab/chrono-mcp/duration_between's live status: https://glimind.com/tool/mcp-registry/io.github.nexus-api-lab/chrono-mcp/duration_between.