mcp-registry/io.tinyfn/tinyfn/business_days / alternatives

Live alternatives to mcp-registry/io.tinyfn/tinyfn/business_days

The best live alternatives to mcp-registry/io.tinyfn/tinyfn/business_days right now are mcp-registry/ai.signal8/mcp/get_policy_trade_overlap, mcp-registry/io.github.pipeworx-io/nyc-parks/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/datos-ar/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/epo-ops/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/epa-echo/polymarket_edge_tracker — capability-matched and ranked by current reliability. mcp-registry/io.tinyfn/tinyfn/business_days itself is currently "healthy".

alternative	server
mcp-registry/ai.signal8/mcp/get_policy_trade_overlap	ai.signal8/mcp	live status →
mcp-registry/io.github.pipeworx-io/nyc-parks/polymarket_edge_tracker	io.github.pipeworx-io/nyc-parks	live status →
mcp-registry/io.github.pipeworx-io/datos-ar/polymarket_edge_tracker	io.github.pipeworx-io/datos-ar	live status →
mcp-registry/io.github.pipeworx-io/epo-ops/polymarket_edge_tracker	io.github.pipeworx-io/epo-ops	live status →
mcp-registry/io.github.pipeworx-io/epa-echo/polymarket_edge_tracker	io.github.pipeworx-io/epa-echo	live status →
mcp-registry/io.github.pipeworx-io/dati-it/polymarket_edge_tracker	io.github.pipeworx-io/dati-it	live status →
mcp-registry/io.github.pipeworx-io/futuur/polymarket_edge_tracker	io.github.pipeworx-io/futuur	live status →
mcp-registry/io.github.pipeworx-io/figma/polymarket_edge_tracker	io.github.pipeworx-io/figma	live status →
mcp-registry/io.github.pipeworx-io/whiskyhunter/polymarket_edge_tracker	io.github.pipeworx-io/whiskyhunter	live status →
mcp-registry/io.github.pipeworx-io/meteors/polymarket_edge_tracker	io.github.pipeworx-io/meteors	live status →
mcp-registry/io.github.pipeworx-io/mempool-space/polymarket_edge_tracker	io.github.pipeworx-io/mempool-space	live status →
mcp-registry/io.github.pipeworx-io/makstat-mk/polymarket_edge_tracker	io.github.pipeworx-io/makstat-mk	live status →

FAQ

What is the best alternative to mcp-registry/io.tinyfn/tinyfn/business_days?

mcp-registry/ai.signal8/mcp/get_policy_trade_overlap is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/nyc-parks/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/datos-ar/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/epo-ops/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/epa-echo/polymarket_edge_tracker. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.tinyfn/tinyfn/business_days down right now?

mcp-registry/io.tinyfn/tinyfn/business_days's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.tinyfn%2Ftinyfn%2Fbusiness_days.

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.tinyfn%2Ftinyfn%2Fbusiness_days or MCP find_alternatives. Check mcp-registry/io.tinyfn/tinyfn/business_days's live status: https://glimind.com/tool/mcp-registry/io.tinyfn/tinyfn/business_days.