ShotPulled

Name: ShotPulled
Author: com.shotpulled

MCP serverMCP

Espresso dialing: log a shot, say how it tasted, get one change in your grinder's own clicks.

by com.shotpulledhomepage ↗v1.3.7

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"shotpulled","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability108/108 checks ok

Tools observed via MCP handshake

register_grinder — Register a manual or electric grinder with its dial settings scheme. It becomes the active grinder only when no grinder is in use (none active, or the active on
set_grinder_position — Set the current grinder collar position. source="measured" resets verification freshness. It replaces the stored position; no history of earlier positions is ke
register_machine — Register an espresso or alternative preparation machine. It becomes the active machine only when no machine is in use (none active, or the active one archived);
set_equipment_archived — Archive or restore a grinder, machine, water, or scale.
update_grinder — Correct a registered grinder — its name, burrs, collar scheme, nominal step, layout, range or notes. Only the keys you send in fields change; send null to clear
update_machine — Correct a registered machine — its name, control type, prep type and style, basket, boiler, accessories or notes — or record where its selectors stand (settings
update_scale — Correct a registered scale — its type, resolution, capacity, capabilities, build or notes. Only the keys you send in fields change; send null to clear an option
update_water — Correct a registered water — its name, type, mineral figures or notes. Only the keys you send in fields change; send null to clear an optional field (an empty s
log_maintenance — Log a cleaning or maintenance job against a piece of equipment. A task that takes the thing apart opens a calibration epoch, and every recipe locked before it i
set_maintenance_offset — Record how far a maintenance job moved the reference, on an entry that opened a calibration epoch. Takes an ENTRY, not a piece of equipment: the offset belongs
set_maintenance_schedule — Set the user's own schedule for one maintenance task on one grinder or machine: their own interval, switching it off, or muting the reminder until a date. Only
get_maintenance_guides — Step-by-step maintenance guides — tools, supplies, steps and warnings, in our own words with the maker's documents as sources. With no arguments, every guide fo
list_maintenance_due — What maintenance is due across the user's current grinders and machines, most urgent first — for "is anything due?". Only tasks with an interval compete: a task
register_water — Register a custom or commercial water formulation.
list_waters — List registered waters for the account. The `id` on each row is the number this account knows that record by, counting from 1 — safe to show, and what other too
register_scale — Register a brewing scale — the instrument that weighs the dose and the yield.
list_scales — List registered scales for the account. The `id` on each row is the number this account knows that record by, counting from 1 — safe to show, and what other too
register_program — Register a programmed shot button on a machine. A program cuts the shot off either by weight (program_type "volumetric", set target_volume_g) or by time (progra
register_coffee — Register a coffee that is NOT yet in list_beans, together with its first bag. It does not switch a coffee in use: it becomes active only when no coffee is in us
set_active — Switch the active bean, grinder or machine for this account. The numbers come from list_beans, list_grinders and list_machines. Registering a coffee, grinder or
update_bean — Update a coffee's own fields (roaster, origins, roast level, rest window, notes, rating…). Bag-shaped fields sent here (state, roast_date, bag_weight_g, grams_r
get_dial_state — Retrieve current dialing state, active context, recent shots, recommendations, and locked recipes.
log_shot — Log an espresso or alternative shot/brew attempt. Uses the active context (bean/grinder/machine/program) unless overridden via bean_id/grinder_id/machine_id/pro
lock_recipe — Lock a successful shot as the reference dialing recipe for this equipment profile. It overwrites the recipe already locked for the same coffee, grinder, machine
delete_shot — Delete a logged shot from history. Restores the bean's remaining weight (which is derived from logged doses). Hard delete — there is no undo. To fix a mistake o
update_shot — Correct fields on an already-logged shot in place — no need to delete and re-log. Use for fixing a wrong dose/yield/time or grind label, re-filing a shot onto t
list_recipes — List recipes (all or filtered by equipment and status). The `id` on each row is the number this account knows that record by, counting from 1 — safe to show, an
get_stats — Get compact flat usage stats for a grinder, machine, or bean.
list_grinders — List grinders registered for the account, with status filter. The `id` on each row is the number this account knows that record by, counting from 1 — safe to sh
list_machines — List machines registered for the account, with status filter. The `id` on each row is the number this account knows that record by, counting from 1 — safe to sh
list_beans — List the coffees registered for the account, with status filter. Each coffee carries its bags[] (every purchase, with its own freshness and grams left) and curr
grinder_math — Determine steps/clicks difference and directions between setting labels (C3).
compute_age — Compute a bag's age in days off roast and its resting/staling verdict — the coffee's current bag by default, or the bag named.
diagnose_shot — Evaluate shot metrics to provide ranked hypotheses (C6) and warn on flip-flops (G2) or fatigue (G6). Resolves the SHOT's own bean — age computed at the shot's p
suggest_next_step — Retrieve the single next experiment step from the reasoning engine.
log_recommendation — Log a recommended dialing change to allow contradiction/oscillation checking (G2).
get_rule — Retrieve the detailed text of a specific rule from the knowledge base by its rule ID.
get_kb_version — Retrieve the current version of the knowledge base.
kb_changelog — Retrieve the changelog showing updates and version differences for the knowledge base.
diagnose_preview — Sandbox-only diagnosis, writes nothing (no verdict, no recommendation-trail entry). Two modes: pass shot_id to dry-run a LOGGED shot (optionally overriding its
list_shots — List shot history with support for pagination and filtering. Every shot carries a derived taste_pending flag (1 = logged with no sensory tags, no rating, and no
register_bag — Register another bag of a coffee that is already in list_beans — the same roaster's product, bought again. It keeps the coffee's recipes, notes and history; onl
update_bag — Change bag-level facts on one bag of a coffee: open, seal, freeze, thaw or finish it, correct its roast date, weight, grams left or price. Bag numbers come from
merge_beans — Fold one coffee into another when the same coffee was registered twice. Every bag, shot, recipe and recommendation of from_bean_id moves to into_bean_id; the ac

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	124 ms	server shotpulled 1.3.7 · protocol 2025-06-18 · 44 tools
11 h ago	mcp initialize	ok	200	129 ms	server shotpulled 1.3.7 · protocol 2025-06-18 · 44 tools
18 h ago	mcp initialize	ok	200	53 ms	server shotpulled 1.3.7 · protocol 2025-06-18 · 44 tools
25 h ago	mcp initialize	ok	200	64 ms	server shotpulled 1.3.7 · protocol 2025-06-18 · 44 tools
32 h ago	mcp initialize	ok	200	103 ms	server shotpulled 1.3.7 · protocol 2025-06-18 · 44 tools
2 d ago	mcp initialize	ok	200	52 ms	server shotpulled 1.3.7 · protocol 2025-06-18 · 44 tools
2 d ago	mcp initialize	ok	200	68 ms	server shotpulled 1.3.7 · protocol 2025-06-18 · 44 tools
2 d ago	mcp initialize	ok	200	80 ms	server shotpulled 1.3.7 · protocol 2025-06-18 · 44 tools
2 d ago	mcp initialize	ok	200	95 ms	server shotpulled 1.3.7 · protocol 2025-06-18 · 44 tools
3 d ago	mcp initialize	ok	200	50 ms	server shotpulled 1.3.7 · protocol 2025-06-18 · 44 tools

ShotPulled

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from