Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PocketCaddie

REMOTE · POCKETCADDIE.IO

Golf drills, ball-flight fixes and range or home practice plans from the PocketCaddie library.

Available components

+3 this week 78 Trust /100

Last scanned (23 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability78
  • 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 1633 tokens (~136/item across 12 items; 11 tools + 1 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 44% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Changelog

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.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “progress” rewrote its description, which is the text the model reads security
    • Tool “recent_sessions” rewrote its description, which is the text the model reads security
    • Tool “session_detail” rewrote its description, which is the text the model reads security
  • 28 Oct 26 0
    • Tool “progress” rewrote its description, which is the text the model reads security
    • Tool “session_detail” rewrote its description, which is the text the model reads security
    • Schema quality: 1320 → 1493 ▼ functional
    • New tool “goals” functional
  • 27 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “practice_plan” rewrote its description, which is the text the model reads security
    • Tool coverage: 46% → 41% ▼ functional
    • Schema quality: 159 → 120 ▲ functional
    • New tool “coach_plan” functional
    • New tool “progress” functional
    • New tool “recent_sessions” functional
    • New tool “rounds” functional
    • New tool “session_detail” functional
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1
    • Resource “PocketCaddie drills” now points somewhere else: ui://pocketcaddie/drills-v4.html → ui://pocketcaddie/drills-v7.html security
    • Tool “about_pocketcaddie” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 4 Nov 2026 · Probed https://pocketcaddie.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.pocketcaddie.io CN=YR2,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 RSA 2048 SHA256-RSA 642abb2cdb06e1a07f9175ef3bfcabcf7f8
SANs: *.pocketcaddie.io, pocketcaddie.io
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pocketcaddie.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
pocketcaddie.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pocketcaddie.io/mcp Verified 200
http (plaintext) http://pocketcaddie.io/mcp HTTPS enforced 308 https://pocketcaddie.io/mcp
MCP tools · 11 exposed · ~1,377 tokens

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 →

Tool Tokens
about_pocketcaddie ~69

Use this when someone asks what PocketCaddie is, how it works, what it measures, which phones and watches it supports, what it costs, or whether an iPhone or Apple Watch can track a golf swing without video. Returns PocketCaddie's own description of itself.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

coach_plan ~39

Use this when a linked golfer asks what their coach assigned: the active PocketCaddie Coach plans, their drills and targets, and progress on each.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

diagnose_ball_flight ~193

Use this when a golfer describes what the ball does or how they hit it, without naming the swing fault: e.g. 'my ball starts left and curves right', 'everything goes right', 'I keep hitting behind the ball', 'I top it', 'I shanked three in a row', 'my shots are weak and short'. Map their words to start direction, curve and contact (leave out what they didn't say). Returns the likely faults from a fixed ball-flight table and the PocketCaddie drills for each, as cards.

NameTypeReqDescription
contactstring–fat = ground first, thin = topped or bladed, shank = off the hosel, weak = short with no compression.
curvestring–Which way it curves in the air.
left_handedboolean––
startstring–Where the ball starts, from the golfer's view.

No output schema declared.

No examples provided.

get_drill ~61

Use this when the golfer wants the full instructions for one drill: steps, the cue to remember, reps, equipment and why it works. Takes a drill id from search_drills, diagnose_ball_flight or practice_plan.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

goals ~127

Use this when a linked golfer asks about their goals, what they're working on, their focus, or how a block of practice went: the active focus goal (the reading, its zone, who set it, the block so far and the before), the long-term goal, goals waiting in the app, and recent goals with the app's outcome (Improved, Held, Not yet, Mastered). Counts are focus swings in the zone out of focus swings with a read. Only call a change real when the outcome says so.

NameTypeReqDescription
recentinteger–How many finished goals to include.

No output schema declared.

No examples provided.

practice_plan ~125

Use this when a golfer asks for a practice plan, a range routine or a session to do at home, e.g. 'build me a 30-minute range plan', 'what should I do with a bucket of balls', 'home practice for tempo'. Builds a timed plan from PocketCaddie drills for 1–3 skills (map their goal to the closest skills). If the golfer has linked their account, call progress first and pass their lowest-scoring skills.

NameTypeReqDescription
minutesinteger––
skillsarrayyes–
wherestring––

No output schema declared.

No examples provided.

progress ~90

Show how the golfer's swing has changed across sessions: Swing Score and skill scores per session (where synced), On target and the stats to work on for newer sessions, the focus score of each focus session, and the first-vs-latest medians of each measurement. Use it to find their weakest skills before practice_plan; use goals for how a focus goal is going.

NameTypeReqDescription
daysinteger––

No output schema declared.

No examples provided.

recent_sessions ~81

List the golfer's most recent PocketCaddie range sessions: date, swings, minutes, sensors used and Swing Score (0–100, needs 15+ swings). Newer sessions report On target instead (the share of swings in range, compared only with the golfer's own normal) with the stats to work on.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

rounds ~56

Use this when a linked golfer asks about their golf rounds or handicap: recent Live Rounds (course, holes, strokes, to par, putts) and the handicap the PocketCaddie app tracks.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

search_drills ~344

Use this when a golfer asks how to fix a swing fault, asks for golf drills, or wants something to work on at the driving range or at home. Covers: slice, hook, shanks, hitting it fat or thin, topping, over the top, casting, early release, flipping, chicken wing, early extension, standing up, sway, reverse pivot, hanging back, all arms, rushed tempo, decelerating, tension, blocks, weak strike. Examples: 'how do I fix my slice', 'I come over the top', 'why do I hit it fat', 'drills for my driver', 'what should I practice at the range'. Pass the golfer's own words as query. Returns drill cards from the PocketCaddie library (48 drills with steps, a cue and reps). If the golfer describes a ball flight or contact problem without naming a fault ('my ball curves right', 'I keep hitting the ground first'), use diagnose_ball_flight instead. Don't use it for tee times, course info, equipment prices, distances or rules. Skills: Tempo, Smoothness, Power, Consistency, Transition, Follow-through, Backswing Turn, Follow-Through Turn, Wrist Action, Swing Path, Body Turn, Head Stability, Kinetic Sequence, Hand Speed, Shoulder Turn, X-Factor, Posture.

NameTypeReqDescription
limitinteger––
max_minutesinteger––
querystring–The golfer's problem or goal in their words.
skillstring–Optional skill name, e.g. Tempo or Backswing Turn.
wherestring–Where they will practice.

No output schema declared.

No examples provided.

session_detail ~192

Break down one range session: Swing Score, its areas and skill scores when the app synced them, plus the median of each swing measurement (tempo, backswing/downswing time, hip turn, posture; shoulder turn, X-Factor and hand speed with Apple Watch; head stability with AirPods). For a focus session, how many focus swings landed in the zone vs before; What your swing shows (patterns) when the app synced them. Newer sessions report On target and every stat as "k of n in range" (Work on, Good, Watch) instead of a Swing Score; On target is relative to the golfer's own normal, never a comparison with anyone else. Defaults to the latest session. Only interpret what is returned; PocketCaddie does not measure ball flight, carry or club head speed.

NameTypeReqDescription
session_idstring–From recent_sessions. Omit for the latest.

No output schema declared.

No examples provided.

Install

How do I install the PocketCaddie MCP server?

PocketCaddie is a hosted endpoint at https://pocketcaddie.io/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 · pocketcaddie.io

# add to Claude Code
claude mcp add --transport http io-pocketcaddie-drills 'https://pocketcaddie.io/mcp'
Common questions

What is the PocketCaddie MCP server?

PocketCaddie is an MCP server listed in the public MCP registry as io.pocketcaddie/drills. Golf drills, ball-flight fixes and range or home practice plans from the PocketCaddie library. This page covers its hosted endpoint (https://pocketcaddie.io/mcp).

Is the PocketCaddie MCP server safe to use?

PocketCaddie scores 78 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 PocketCaddie MCP server expose?

PocketCaddie exposes 11 tools: search_drills, get_drill, practice_plan, diagnose_ball_flight, about_pocketcaddie, and 6 more. Their descriptions and schemas cost roughly 1,377 tokens of context every time the server is loaded.

Does the PocketCaddie MCP server require authentication?

No. We connected to PocketCaddie without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PocketCaddie MCP server still maintained?

PocketCaddie is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.