Home / MCP registry index / dev.anatome/anatome
dev.anatome/anatome
dev.anatome/anatome in the official MCP registry.
Endpoint https://anatome.dev/mcp.
The registry describes it as: Log workouts and meals by telling your AI. 873 exercises, muscle diagrams, food lookup.
We read its 36 tools on 2026-10-28. 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
search_exercises get_exercise resolve_exercise list_muscles generate_muscle_image list_routines get_routine instantiate_routine search_foods lookup_barcode log_workout get_workouts log_meal get_meals log_water log_body_metric get_body_metrics upsert_profile get_profile log_cardio get_cardio_activities ai_parse_meal ai_photo_macros ai_meal_plan ai_workout_plan get_muscle_recovery get_nutrition_daily get_water update_meal delete_meal update_sets delete_workout export_data get_events my_training_context get_progress
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-anatome-anatome)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.