mcp-registry/com.currencyguard/guard-pricing/resolve_settlement_date / alternatives

Live alternatives to mcp-registry/com.currencyguard/guard-pricing/resolve_settlement_date

The best live alternatives to mcp-registry/com.currencyguard/guard-pricing/resolve_settlement_date right now are mcp-registry/ai.ohmyfin/banking-intelligence/value_date, mcp-registry/io.github.solvohq/openworkdays/businessdays, mcp-registry/io.github.zev-lll/lastlook-data/get_fx_rate_by_date, mcp-registry/dev.exchangerate/mcp/get_range, mcp-registry/io.github.qinisolabs/qiniso/parse_date — capability-matched and ranked by current reliability. mcp-registry/com.currencyguard/guard-pricing/resolve_settlement_date itself is currently "healthy".

alternative	server
mcp-registry/ai.ohmyfin/banking-intelligence/value_date	ai.ohmyfin/banking-intelligence	live status →
mcp-registry/io.github.solvohq/openworkdays/businessdays	io.github.SolvoHQ/openworkdays	live status →
mcp-registry/io.github.zev-lll/lastlook-data/get_fx_rate_by_date	io.github.zev-lll/lastlook-data	live status →
mcp-registry/dev.exchangerate/mcp/get_range	dev.exchangerate/mcp	live status →
mcp-registry/io.github.qinisolabs/qiniso/parse_date	io.github.qinisolabs/qiniso	live status →
mcp-registry/io.github.toreva/kit/toreva_perps_funding_settle	io.github.toreva/kit	live status →
mcp-registry/io.github.pipeworx-io/frankfurter/get_timeseries	io.github.pipeworx-io/frankfurter	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_timestamp_get	xyz.558686.gpt55/token-gateway	live status →
mcp-registry/io.github.zev-lll/lastlook-data/get_treasury_yield_by_date	io.github.zev-lll/lastlook-data	live status →
mcp-registry/dev.nexbid/discovery/settle	dev.nexbid/discovery	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_timestamp	xyz.558686.gpt55/token-gateway	live status →
mcp-registry/ai.signal8/mcp/get_historical_prices	ai.signal8/mcp	live status →

FAQ

What is the best alternative to mcp-registry/com.currencyguard/guard-pricing/resolve_settlement_date?

mcp-registry/ai.ohmyfin/banking-intelligence/value_date is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.solvohq/openworkdays/businessdays, mcp-registry/io.github.zev-lll/lastlook-data/get_fx_rate_by_date, mcp-registry/dev.exchangerate/mcp/get_range, mcp-registry/io.github.qinisolabs/qiniso/parse_date. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.currencyguard/guard-pricing/resolve_settlement_date down right now?

mcp-registry/com.currencyguard/guard-pricing/resolve_settlement_date's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.currencyguard%2Fguard-pricing%2Fresolve_settlement_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%2Fcom.currencyguard%2Fguard-pricing%2Fresolve_settlement_date or MCP find_alternatives. Check mcp-registry/com.currencyguard/guard-pricing/resolve_settlement_date's live status: https://glimind.com/tool/mcp-registry/com.currencyguard/guard-pricing/resolve_settlement_date.