List your agent

ShotPulled

MCP server● Hosted · onlinev1.4.2

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

Reviews

No review yet. Used ShotPulled? Be the first to help others choose.

What it does

ShotPulled is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.4.2
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 8h ago (live check)

Hosted endpoint

  • https://mcp.shotpulled.com/mcp streamable-http

In Claude Code: claude mcp add --transport http shotpulled https://mcp.shotpulled.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "shotpulled": {
      "url": "https://mcp.shotpulled.com/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 8h ago

ONLINE ShotPulled answered an MCP connection on 16 Nov 2026 and introduced itself as shotpulled 1.4.2 (MCP protocol 2025-06-18).

44 tools offered to AI assistants

  • 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 one archived); otherwise call set_active with its grinder_id to switch to it. The
  • 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 kept.
  • 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); otherwise call set_active with its machine_id to switch to it. The `active` fie
  • 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 an optional field (an empty string also clears a text field, but not a number or
  • 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). Only the keys you send in fields change; send null to clear an optional field
  • 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 optional field (an empty string also clears a text field, but not a number or a closed
  • 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 string also clears a text field, but not a number or a closed list). Required fiel
  • 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 is read through that epoch's offset. Record the offset here if you counted the cl
  • 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 to the event that caused it, which is what lets several of them compose for a re
  • 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 the keys you send in fields change; send every: null to go back to the maker's g
  • 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 for the user's current grinders and machines (and the water filter fitted in each).
Show 32 more
  • list_maintenance_due · What maintenance is due across the user's current grinders and machines, most urgent first. Use it for "is anything due?". Only tasks with an interval compete: a task the machine counts and signals itself, one done by habit or when a sympto
  • 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 tools expect back.
  • 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 tools expect back.
  • 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 (program_type "timed", set target_time_s). One machine can have a mix of both. A 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 use (none active, or the active one archived or with every bag finished); otherwis
  • 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 machine makes it active only when nothing of that kind is in use (the `active`
  • 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_remaining, cost…) land on the coffee's CURRENT bag. Use update_bag when it has mo
  • 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/program_id. ALWAYS pass bean_id explicitly when the user names a specific coffee, s
  • 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, program and drink intent, which keeps its recipe_id.
  • 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 on an otherwise-valid shot, prefer update_shot over delete-and-relog.
  • update_shot · Correct fields on an already-logged shot in place, with no need to delete and re-log. Use for fixing a wrong dose/yield/time or grind label, re-filing a shot onto the right bean (bean_id), backfilling rating/tasting notes, or fixing the tim
  • 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, and what other tools expect back.
  • 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 show, and what other tools expect back. Each row carries its maintenance block: eve
  • 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 show, and what other tools expect back. Each row carries its maintenance block, res
  • 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 current_bag_id; the row's top-level roast_date, state, grams_remaining and age field
  • 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, for the coffee's current bag by default or for 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 pulled_at), never the active profile, and echoes it as bean_context, so diagnosing
  • 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 sensory_tags, for the "what would this read as?" preview; the shot's own bean an
  • 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 tasted flip: the tasting is still owed and can be backfilled with update_shot).
  • 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; only the purchase facts (roast date, weight, price, state) are new. Does not change
  • 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 the bags[] on list_beans (or current_bag_id). For the coffee itself (roaster, o
  • 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 active coffee follows if it was the one merged away; origins move only if the targ

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Version1.4.2DECLAREDSRC-001 Official MCP Registry1d ago
Hosted endpointhttps://mcp.shotpulled.com/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://shotpulled.comDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

  • VERSION26 Oct 2026
    1.4.1 → 1.4.2
  • VERSION24 Oct 2026
    1.3.7 → 1.4.1
  • VERSION04 Oct 2026
    1.3.5 → 1.3.7
  • VERSION02 Oct 2026
    1.3.4 → 1.3.5
  • VERSION29 Sept 2026
    1.3.3 → 1.3.4
  • VERSION28 Sept 2026
    1.3.0 → 1.3.3
  • VERSION27 Sept 2026
    1.0.2 → 1.3.0

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run ShotPulled? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor ShotPulledLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of ShotPulled?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/shotpulled?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/shotpulled/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about ShotPulled

How do I connect ShotPulled?

Use the hosted endpoint https://mcp.shotpulled.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does ShotPulled offer?

When Electra Index connected on 16 Nov 2026, it listed 44 tools: register_grinder, set_grinder_position, register_machine, set_equipment_archived, update_grinder, update_machine, update_scale, update_water and more. The full list is in "Live check" above.

Is ShotPulled online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 8h ago.