mcp-registry/io.github.zev-lll/lastlook-data/get_value_by_date / alternatives

Live alternatives to mcp-registry/io.github.zev-lll/lastlook-data/get_value_by_date

The best live alternatives to mcp-registry/io.github.zev-lll/lastlook-data/get_value_by_date right now are mcp-registry/io.github.findimitrov/fintel-discovery/GetFredSeriesData, mcp-registry/io.github.blackboxfoundry/livedatalink/fred_observations, mcp-registry/io.github.findimitrov/fintel-discovery/SearchFredSeries, mcp-registry/io.github.blackboxfoundry/livedatalink/fred_compare, mcp-registry/io.github.blackboxfoundry/livedatalink/fred_releases — capability-matched and ranked by current reliability. mcp-registry/io.github.zev-lll/lastlook-data/get_value_by_date itself is currently "healthy".

alternative	server
mcp-registry/io.github.findimitrov/fintel-discovery/GetFredSeriesData	io.github.findimitrov/fintel-discovery	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/fred_observations	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.findimitrov/fintel-discovery/SearchFredSeries	io.github.findimitrov/fintel-discovery	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/fred_compare	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/fred_releases	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/com.olyport/fred/get_series_observations	com.olyport/fred	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/fred_series_info	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.pipeworx-io/macro-snapshot/indicator	io.github.pipeworx-io/macro-snapshot	live status →
mcp-registry/com.olyport/fred/get_release_dates	com.olyport/fred	live status →
mcp-registry/com.olyport/fred/search_series	com.olyport/fred	live status →
mcp-registry/dev.exchangerate/mcp/get_range	dev.exchangerate/mcp	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/fred_search	io.github.blackboxfoundry/livedatalink	live status →

FAQ

What is the best alternative to mcp-registry/io.github.zev-lll/lastlook-data/get_value_by_date?

mcp-registry/io.github.findimitrov/fintel-discovery/GetFredSeriesData is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.blackboxfoundry/livedatalink/fred_observations, mcp-registry/io.github.findimitrov/fintel-discovery/SearchFredSeries, mcp-registry/io.github.blackboxfoundry/livedatalink/fred_compare, mcp-registry/io.github.blackboxfoundry/livedatalink/fred_releases. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.zev-lll/lastlook-data/get_value_by_date down right now?

mcp-registry/io.github.zev-lll/lastlook-data/get_value_by_date's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.zev-lll%2Flastlook-data%2Fget_value_by_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%2Fio.github.zev-lll%2Flastlook-data%2Fget_value_by_date or MCP find_alternatives. Check mcp-registry/io.github.zev-lll/lastlook-data/get_value_by_date's live status: https://glimind.com/tool/mcp-registry/io.github.zev-lll/lastlook-data/get_value_by_date.