Home / MCP registry index / ai.loafy/loafy
Loafy: Sourdough Bread Baking
ai.loafy/loafy in the official MCP registry.
Endpoint https://loafy.ai/mcp.
The registry describes it as: Sourdough baking: dough calculators, a bake planner, The Sourdough Framework and your bake journal
We read its 19 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
calculate_bread_dough calculate_pizza_dough plan_sourdough_bake list_sourdough_journeys start_sourdough_journey get_sourdough_journey_step find_sourdough_answer search_sourdough_book get_sourdough_book_contents read_sourdough_book list_my_bakes log_bake update_bake list_my_starters add_starter update_starter list_my_containers add_container update_container
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-loafy-loafy)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.