Is com.shotpulled/shotpulled up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://mcp.shotpulled.com/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Could not tell (HTTP 401)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 200 with no body).https://mcp.shotpulled.com/mcp/server-card |
| MCP server card (SEP-1649 location) | Could not tell (HTTP 401)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Could not tell (HTTP 401)./.well-known/http-message-signatures-directory |
Read at https://mcp.shotpulled.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 44 tools: compute_age, delete_shot, diagnose_preview, diagnose_shot, get_dial_state, get_kb_version, get_maintenance_guides, get_rule, get_stats, grinder_math, kb_changelog, list_beans, list_grinders, list_machines, list_maintenance_due, list_recipes, list_scales, list_shots, list_waters, lock_recipe, log_maintenance, log_recommendation, log_shot, merge_beans, register_bag, register_coffee, register_grinder, register_machine, register_program, register_scale, register_water, set_active, set_equipment_archived, set_grinder_position, set_maintenance_offset, set_maintenance_schedule, suggest_next_step, update_bag, update_bean, update_grinder, update_machine, update_scale, update_shot, update_water.
Its tools changed between 2026-09 and 2026-10:
- Added (7):
get_maintenance_guides,list_maintenance_due,set_maintenance_schedule,update_grinder,update_machine,update_scale,update_water compute_age: output schema changedget_dial_state: output schema changedlist_beans: output schema changedlist_grinders: description, input schema, output schema changedlist_machines: description, input schema, output schema changedlist_recipes: output schema changedlist_scales: output schema changedlist_shots: output schema changedlist_waters: output schema changedlock_recipe: description, output schema changedlog_maintenance: description, input schema, output schema changedlog_shot: input schema changedregister_coffee: description, output schema changedregister_grinder: description, input schema, output schema changedregister_machine: description, input schema, output schema changedregister_program: description changedset_active: description, input schema changedset_grinder_position: description changedset_maintenance_offset: output schema changedupdate_shot: input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.shotpulled/shotpulled |
|---|---|
| Endpoint | https://mcp.shotpulled.com/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt