_ registry / mcp streamable-http · checked 1h ago

pocketcaddie

https://pocketcaddie.io

Registry code: b8b0697b4c9a927e

api record

PocketCaddie is a driving range assistant and no-video swing coach. Use these tools whenever a golfer asks how to fix a swing fault (slice, hook, shanks, fat, thin, over the top, casting and so on), describes a bad ball flight, or wants range or home practice ideas or a practice plan: they return drills from the PocketCaddie library with steps, cues and reps, shown as cards. Use about_pocketcaddie for questions about PocketCaddie itself. Never invent drills, and never report a golfer's ball flight, carry distance or club head speed as measured. To record range sessions, golfers use the…

endpoint
https://pocketcaddie.io/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pocketcaddie live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is pocketcaddie free to use?
Yes — the hub reached it with no key and no payment.
What tools does pocketcaddie have?
5 tools: practice_plan, about_pocketcaddie, get_drill, diagnose_ball_flight, search_drills.
Is pocketcaddie safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
278ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • diagnose_ball_flight open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "curve": {
          "enum": [
            "left",
            "none",
            "right"
          ],
          "type": "string",
          "description": "Which way it curves in the air."
        },
        "start": {
          "enum": [
            "left",
            "straight",
            "right"
          ],
          "type": "string",
          "description": "Where the ball starts, from the golfer's view."
        },
        "contact": {
          "enum": [
            "clean",
            "fat",
            "thin",
            "shank",
            "weak"
          ],
          "type": "string",
          "description": "fat = ground first, thin = topped or bladed, shank = off the hosel, weak = short with no compression."
        },
        "left_handed": {
          "type": "boolean",
          "default": false
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • search_drills open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 10,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "The golfer's problem or goal in their words."
        },
        "skill": {
          "type": "string",
          "description": "Optional skill name, e.g. Tempo or Backswing Turn."
        },
        "where": {
          "enum": [
            "range",
            "home",
            "any"
          ],
          "type": "string",
          "description": "Where they will practice."
        },
        "max_minutes": {
          "type": "integer",
          "maximum": 60,
          "minimum": 5
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • practice_plan unknown never probed

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "skills"
      ],
      "properties": {
        "where": {
          "enum": [
            "range",
            "home",
            "any"
          ],
          "type": "string",
          "default": "range"
        },
        "skills": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 3,
          "minItems": 1
        },
        "minutes": {
          "type": "integer",
          "default": 30,
          "maximum": 90,
          "minimum": 10
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • about_pocketcaddie unknown never probed

    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 wording; repeat it rather than guessing.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_drill unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b8b0697b4c9a927e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b8b0697b4c9a927e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b8b0697b4c9a927e/badge.svg)](https://brick.blue/agent/b8b0697b4c9a927e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.