mcp-registry/io.github.nexus-api-lab/chrono-mcp/duration_between / alternatives

Live alternatives to mcp-registry/io.github.nexus-api-lab/chrono-mcp/duration_between

The 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".

alternativeserver
mcp-registry/io.tinyfn/tinyfn/time_differenceio.tinyfn/tinyfnlive status →
mcp-registry/io.tinyfn/tinyfn/date_diffio.tinyfn/tinyfnlive status →
mcp-registry/io.tinyfn/tinyfn/business_daysio.tinyfn/tinyfnlive status →
mcp-registry/io.tinyfn/tinyfn/subtract_timeio.tinyfn/tinyfnlive status →
mcp-registry/io.github.foundrynet/foundrynet-geo/distanceio.github.FoundryNet/foundrynet-geolive status →
mcp-registry/io.tinyfn/tinyfn/subtract_time_2io.tinyfn/tinyfnlive status →
mcp-registry/io.tinyfn/tinyfn/format_durationio.tinyfn/tinyfnlive status →
mcp-registry/site.jiebang.www/tools/timezone_convertsite.jiebang.www/toolslive status →
mcp-registry/com.wingmanprotocol.agent/gateway/date_diffcom.wingmanprotocol.agent/gatewaylive status →
mcp-registry/com.wingmanprotocol.agent/gateway/date_addcom.wingmanprotocol.agent/gatewaylive status →
mcp-registry/io.tinyfn/tinyfn/seconds_to_hmsio.tinyfn/tinyfnlive status →
mcp-registry/io.github.solvohq/openworkdays/businessdaysio.github.SolvoHQ/openworkdayslive status →

FAQ

What is the best alternative to mcp-registry/io.github.nexus-api-lab/chrono-mcp/duration_between?

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.

Is mcp-registry/io.github.nexus-api-lab/chrono-mcp/duration_between down right now?

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.

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.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.