Home / MCP registry index / com.shotpulled/shotpulled
ShotPulled
com.shotpulled/shotpulled in the official MCP registry.
Endpoint https://mcp.shotpulled.com/mcp.
The registry describes it as: Espresso dialing: log a shot, say how it tasted, get one change in your grinder's own clicks.
We read its 44 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
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
register_grinder set_grinder_position register_machine set_equipment_archived update_grinder update_machine update_scale update_water log_maintenance set_maintenance_offset set_maintenance_schedule get_maintenance_guides list_maintenance_due register_water list_waters register_scale list_scales register_program register_coffee set_active update_bean get_dial_state log_shot lock_recipe delete_shot update_shot list_recipes get_stats list_grinders list_machines list_beans grinder_math compute_age diagnose_shot suggest_next_step log_recommendation get_rule get_kb_version kb_changelog diagnose_preview list_shots register_bag update_bag merge_beans
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-shotpulled-shotpulled)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.