mcp-registry/today.blame/mcp/get_blame_recipe / alternatives

Live alternatives to mcp-registry/today.blame/mcp/get_blame_recipe

The best live alternatives to mcp-registry/today.blame/mcp/get_blame_recipe right now are mcp-registry/io.github.signerlabs/shipswift/getRecipe, mcp-registry/io.github.rodeldoria/savor-dish/recipes_get_random, mcp-registry/io.github.pipeworx-io/dummyjson/recipe, mcp-registry/io.github.pipeworx-io/spoonacular/recipe_summary, mcp-registry/io.github.massed-compute/mcp/recipes_get — capability-matched and ranked by current reliability. mcp-registry/today.blame/mcp/get_blame_recipe itself is currently "healthy".

alternative	server
mcp-registry/io.github.signerlabs/shipswift/getRecipe	io.github.signerlabs/shipswift	live status →
mcp-registry/io.github.rodeldoria/savor-dish/recipes_get_random	io.github.rodeldoria/savor-dish	live status →
mcp-registry/io.github.pipeworx-io/dummyjson/recipe	io.github.pipeworx-io/dummyjson	live status →
mcp-registry/io.github.pipeworx-io/spoonacular/recipe_summary	io.github.pipeworx-io/spoonacular	live status →
mcp-registry/io.github.massed-compute/mcp/recipes_get	io.github.Massed-Compute/mcp	live status →
mcp-registry/app.toolsnap/toolsnap-mcp/task_recipes	app.toolsnap/toolsnap-mcp	live status →
mcp-registry/io.github.rodeldoria/savor-dish/recipes_get	io.github.rodeldoria/savor-dish	live status →
mcp-registry/io.github.pipeworx-io/recipes/random_meal	io.github.pipeworx-io/recipes	live status →
mcp-registry/ai.sugra/api-mcp/get_snapshot	ai.sugra/api-mcp	live status →
mcp-registry/dev.kaimeilabs/guardian-engine/verify_recipe	dev.kaimeilabs/guardian-engine	live status →
mcp-registry/io.github.mnemom/mnemom/report_recipe_fn_fp	io.github.mnemom/mnemom	live status →
mcp-registry/io.github.pipeworx-io/spoonacular/recipe_information	io.github.pipeworx-io/spoonacular	live status →

FAQ

What is the best alternative to mcp-registry/today.blame/mcp/get_blame_recipe?

mcp-registry/io.github.signerlabs/shipswift/getRecipe is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.rodeldoria/savor-dish/recipes_get_random, mcp-registry/io.github.pipeworx-io/dummyjson/recipe, mcp-registry/io.github.pipeworx-io/spoonacular/recipe_summary, mcp-registry/io.github.massed-compute/mcp/recipes_get. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/today.blame/mcp/get_blame_recipe down right now?

mcp-registry/today.blame/mcp/get_blame_recipe's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Ftoday.blame%2Fmcp%2Fget_blame_recipe.

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%2Ftoday.blame%2Fmcp%2Fget_blame_recipe or MCP find_alternatives. Check mcp-registry/today.blame/mcp/get_blame_recipe's live status: https://glimind.com/tool/mcp-registry/today.blame/mcp/get_blame_recipe.