ShotPulled
REMOTE · MCP.SHOTPULLED.COM
Espresso dialing: log a shot, say how it tasted, get one change in your grinder's own clicks.
Available components
Last scanned (23 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 5 Nov 2026.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 8418 tokens (~183/item across 46 items; 44 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 45 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Oct 26 0
- Server version: 1.4.1 → 1.4.2 functional
- 24 Oct 26 0
- Server version: 1.4.0 → 1.4.1 functional
- 23 Oct 26 0
- Tool “compute_age” rewrote its description, which is the text the model reads security
- Tool “delete_shot” rewrote its description, which is the text the model reads security
- Tool “diagnose_preview” rewrote its description, which is the text the model reads security
- Tool “diagnose_shot” rewrote its description, which is the text the model reads security
- Tool “get_maintenance_guides” rewrote its description, which is the text the model reads security
- Tool “list_beans” rewrote its description, which is the text the model reads security
- Tool “list_grinders” rewrote its description, which is the text the model reads security
- Tool “list_machines” rewrote its description, which is the text the model reads security
- Tool “list_maintenance_due” rewrote its description, which is the text the model reads security
- Tool “list_recipes” rewrote its description, which is the text the model reads security
- Tool “list_scales” rewrote its description, which is the text the model reads security
- Tool “list_shots” rewrote its description, which is the text the model reads security
- Tool “list_waters” rewrote its description, which is the text the model reads security
- Tool “log_maintenance” rewrote its description, which is the text the model reads security
- Tool “log_shot” rewrote its description, which is the text the model reads security
- Tool “merge_beans” rewrote its description, which is the text the model reads security
- Tool “register_bag” rewrote its description, which is the text the model reads security
- Tool “register_coffee” rewrote its description, which is the text the model reads security
- Tool “register_scale” rewrote its description, which is the text the model reads security
- Tool “set_maintenance_offset” rewrote its description, which is the text the model reads security
- Tool “set_maintenance_schedule” rewrote its description, which is the text the model reads security
- Tool “update_bag” rewrote its description, which is the text the model reads security
- Tool “update_bean” rewrote its description, which is the text the model reads security
- Tool “update_grinder” rewrote its description, which is the text the model reads security
- Tool “update_machine” rewrote its description, which is the text the model reads security
- Tool “update_scale” rewrote its description, which is the text the model reads security
- Tool “update_shot” rewrote its description, which is the text the model reads security
- Tool “update_water” rewrote its description, which is the text the model reads security
- Server version: 1.3.8 → 1.4.0 functional
- “register_bag” added an optional parameter “catalog_coffee_id” cosmetic
- “register_bag” added an optional parameter “lot_revision_id” cosmetic
- “register_bag” added an optional parameter “product_id” cosmetic
- “register_coffee” added an optional parameter “catalog_coffee_id” cosmetic
- “register_coffee” added an optional parameter “lot_revision_id” cosmetic
- “register_coffee” added an optional parameter “product_id” cosmetic
- “diagnose_preview” reworded the description of “source” cosmetic
- “get_maintenance_guides” reworded the description of “guide_ids” cosmetic
- “list_grinders” reworded the description of “maintenance” cosmetic
- “list_machines” reworded the description of “maintenance” cosmetic
- “log_maintenance” reworded the description of “disturbs_zero” cosmetic
- “log_maintenance” reworded the description of “guide_id” cosmetic
- “log_maintenance” reworded the description of “note” cosmetic
- “log_shot” reworded the description of “data_confidence” cosmetic
- “log_shot” reworded the description of “pulled_at” cosmetic
- “log_shot” reworded the description of “tasted” cosmetic
- “register_bag” reworded the description of “best_by_date” cosmetic
- “register_bag” reworded the description of “buy_date” cosmetic
- “register_bag” reworded the description of “opened_date” cosmetic
- “register_bag” reworded the description of “roast_date” cosmetic
- “register_coffee” reworded the description of “best_by_date” cosmetic
- “register_coffee” reworded the description of “buy_date” cosmetic
- “register_coffee” reworded the description of “frozen_at” cosmetic
- “register_coffee” reworded the description of “notes” cosmetic
- “register_coffee” reworded the description of “opened_date” cosmetic
- “register_coffee” reworded the description of “roast_date” cosmetic
- “register_coffee” reworded the description of “unfrozen_at” cosmetic
- “register_grinder” reworded the description of “catalog_id” cosmetic
- “register_machine” reworded the description of “catalog_id” cosmetic
- “register_machine” reworded the description of “hardness_dh” cosmetic
- “register_machine” reworded the description of “prep_style” cosmetic
- “register_scale” reworded the description of “height_mm” cosmetic
- “register_scale” reworded the description of “resolution_banded” cosmetic
- “register_scale” reworded the description of “width_mm” cosmetic
- “set_maintenance_schedule” reworded the description of “changed_at” cosmetic
- “update_bean” reworded the description of “reason” cosmetic
- 14 Oct 26 0
- Server version: 1.3.7 → 1.3.8 functional
- 4 Oct 26 91
- Stability: 0.97 → pass security
- Tool “list_machines” rewrote its description, which is the text the model reads security
- Tool “update_machine” rewrote its description, which is the text the model reads security
- Server version: 1.3.5 → 1.3.6 functional
- “log_shot” added an optional parameter “machine_settings” cosmetic
- 2 Oct 26 0
- Server version: 1.3.4 → 1.3.5 functional
- 29 Sept 26 0
- Tool “lock_recipe” rewrote its description, which is the text the model reads security
- Tool “register_program” rewrote its description, which is the text the model reads security
- Tool “set_grinder_position” rewrote its description, which is the text the model reads security
- Tool “lock_recipe” is now declared destructive security
- Tool “register_program” is now declared destructive security
- Tool “set_grinder_position” is now declared destructive security
- Tool “set_maintenance_offset” is now declared destructive security
- Tool “set_maintenance_schedule” is now declared destructive security
- Tool “update_bag” is now declared destructive security
- Tool “update_bean” is now declared destructive security
- Tool “update_grinder” is now declared destructive security
- Tool “update_machine” is now declared destructive security
- Tool “update_scale” is now declared destructive security
- Tool “update_shot” is now declared destructive security
- Tool “update_water” is now declared destructive security
- Server version: 1.3.3 → 1.3.4 functional
- 28 Sept 26 0
- Tool “list_maintenance_due” rewrote its description, which is the text the model reads security
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 1.3.1 → 1.3.3 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.shotpulled.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shotpulled.com | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1c220361ae36e3240ea806b1381ece7d |
| SANs: shotpulled.com, *.shotpulled.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.shotpulled.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| shotpulled.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.shotpulled.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.shotpulled.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Protected resource metadata
| Document | https://mcp.shotpulled.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.shotpulled.com/mcp |
| Authorisation server | https://clerk.shotpulled.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.shotpulled.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.shotpulled.com/mcp | HTTPS enforced | 308 | https://mcp.shotpulled.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
update_scale Update a scale ~170
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 list). Required fields can be changed but not cleared. fields may be omitted when only reason is sent. The three capabilities are 1, 0, or null for "the maker never said"; leave one out rather than sending 0 when nobody knows.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | – |
| reason | string | – | Optional note, appended to this record's own notes as an ordinary line. Omit it and nothing is written. |
| scale_id | integer | yes | This account's own scale number, from list_scales. Never guess one. |
| Name | Type | Req | Description |
|---|---|---|---|
| changed_keys | array | yes | – |
| message | string | yes | – |
| scale_id | integer | yes | – |
| status | string | yes | – |
No examples provided.
update_shot Update a shot ~132
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 timestamp (pulled_at). Changing grind_label re-derives the numeric grind position from the shot's grinder; changing yield/time/dose/tds keeps flow rate and extraction yield consistent automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | Only the fields to change |
| shot_id | integer | yes | ID of the shot to correct |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| shot_id | integer | yes | – |
| status | string | yes | – |
| updated_fields | array | yes | – |
No examples provided.
update_water Update a water recipe ~136
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 fields can be changed but not cleared. fields may be omitted when only reason is sent.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | – |
| reason | string | – | Optional note, appended to this record's own notes as an ordinary line. Omit it and nothing is written. |
| water_id | integer | yes | This account's own water number, from list_waters. Never guess one. |
| Name | Type | Req | Description |
|---|---|---|---|
| changed_keys | array | yes | – |
| message | string | yes | – |
| status | string | yes | – |
| water_id | integer | yes | – |
No examples provided.
How do I install the ShotPulled MCP server?
ShotPulled is a hosted endpoint at https://mcp.shotpulled.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.shotpulled.com
claude mcp add --transport http com-shotpulled-shotpulled 'https://mcp.shotpulled.com/mcp'
What is the ShotPulled MCP server?
ShotPulled is an MCP server listed in the public MCP registry as com.shotpulled/shotpulled. Espresso dialing: log a shot, say how it tasted, get one change in your grinder's own clicks. This page covers its hosted endpoint (https://mcp.shotpulled.com/mcp).
Is the ShotPulled MCP server safe to use?
ShotPulled scores 91 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ShotPulled MCP server expose?
ShotPulled exposes 44 tools: register_grinder, set_grinder_position, register_machine, set_equipment_archived, update_grinder, and 39 more. Their descriptions and schemas cost roughly 8,379 tokens of context every time the server is loaded.
Does the ShotPulled MCP server require authentication?
Yes. ShotPulled asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the ShotPulled MCP server still maintained?
ShotPulled is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ShotPulled MCP server?
VerifyMCP ran 13 checks on ShotPulled, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.