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.

io.github.bjornj12/trackman-mcp

PYPI · TRACKMAN-MCP · SCANNED SEP 13

Fetch your Trackman Golf stats (handicap, rounds, shots, club gapping) as MCP tools.

Available components

−15 this week 59 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1509 tokens (~125/item across 12 items; 12 tools + 0 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 Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 21% 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
  • We read all 12 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 current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.bjornj12/trackman-mcp server?

io.github.bjornj12/trackman-mcp runs locally as a PyPI package, launched with uvx trackman-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · trackman-mcp

# add to Claude Code
claude mcp add bjornj12-trackman-mcp -- uvx trackman-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "bjornj12-trackman-mcp": {
      "command": "uvx",
      "args": [
        "trackman-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "bjornj12-trackman-mcp": {
      "command": "uvx",
      "args": [
        "trackman-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add bjornj12-trackman-mcp -- uvx trackman-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bjornj12-trackman-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "trackman-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bjornj12-trackman-mcp --command uvx --arg trackman-mcp
# ~/.hermes/config.yaml
mcp_servers:
  bjornj12-trackman-mcp:
    command: "uvx"
    args: ["trackman-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "bjornj12-trackman-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "trackman-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add bjornj12-trackman-mcp -t stdio -c uvx -a trackman-mcp
// mcp.json
{
  "mcpServers": {
    "bjornj12-trackman-mcp": {
      "command": "uvx",
      "args": [
        "trackman-mcp"
      ]
    }
  }
}
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.

  • 13 Sept 26 −15
    • Malware scan: pass → unverified security
  • 12 Sept 26 +13
    • Malware scan: unverified → pass security
    • Stability: pass → 0.80 functional
  • 11 Sept 26 0
    • Stability: 0.97 → pass security
  • 10 Sept 26 +1

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

  • 8 Sept 26 +1

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

  • 7 Sept 26 −15
    • Malware scan: pass → unverified security
  • 5 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 4 Sept 26 +15
    • Malware scan: unverified → pass security
    • Stability: 0.97 → pass security
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 13 Sept 2026 · Analysed pypi/trackman-mcp@0.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 23 packages
Packages resolved 23
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~1,386 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
auth ~128

Check or (re)establish your Trackman sign-in. Actions: - `status` (default): report whether the current token works and who you're signed in as. Use this first; it never opens anything. - `login`: (re)authenticate. Tries a silent refresh of the saved browser session first; if that's expired and `open_browser` is true, opens a window to sign in once. Use when `status` says expired/not signed in. Never echoes the token.

NameTypeReqDescription
actionstring
open_browserboolean

Structured output declared, but exposes no named fields.

No examples provided.

build_visualization ~196

Render a coaching diagnosis into a self-contained animated HTML page. Returns `{html}` — one standalone document (inline canvas/JS, no network, no external resources) ready to drop straight into a Claude **HTML artifact**. `data` shape (all optional; the viz adapts): {title, subtitle, diagnosis, handedness "RH"|"LH", shots:[{launchDirection,launchAngle,carry,total, totalSide,curve,maxHeight,landingAngle,hangTime}], swing:{clubPath,faceAngle,faceToPath}, targets:[{label,value,target,low, high,met}], blocks:[{name,detail,goal,where "range"|"home", links:[{label,url}]}]}. Renders the measured flight (side view + top-down, animated) and drills grouped range/home. See the trackman-visualizer prompt.

NameTypeReqDescription
dataobjectyes

Structured output declared, but exposes no named fields.

No examples provided.

get_activity_summary ~47

Get activity counts grouped by kind over an optional time window.

NameTypeReqDescription
skipinteger
takeinteger
time_from
time_to

Structured output declared, but exposes no named fields.

No examples provided.

get_club_stats ~66

Get per-club gapping and dispersion ("My Bag" / Find My Distance). For each club: average carry and total, carry/total standard deviation, and the dispersion ellipse. This is the source for gapping analysis.

NameTypeReqDescription
include_retiredboolean

Structured output declared, but exposes no named fields.

No examples provided.

get_course_rounds ~84

Get the player's course rounds (scorecards). Each round includes per-hole scores (score, putts, GIR, hcp strokes) and round aggregates (`stat`: driving, FIR, GIR, putts, score distribution).

NameTypeReqDescription
completedfilter by completion (True = finished rounds only).
skipinteger
takeinteger

Structured output declared, but exposes no named fields.

No examples provided.

get_handicap ~60

Get handicap history: per-round differentials and how the index moved.

NameTypeReqDescription
only_in_avgbooleanonly records counted in the handicap average.
skipintegerpaging offset.
takeintegernumber of records to return.

Structured output declared, but exposes no named fields.

No examples provided.

get_profile ~48

Get the player's profile and current handicap. Returns identity (name, email, nationality, dexterity, category) and the current handicap (`hcp.currentHcp`, plus the most recent handicap record).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_session ~83

Get one activity in full by its id — including shot-level launch metrics. For RANGE_PRACTICE: every stroke with its measurement (ball/club speed, smash, launch, spin, carry, side, curve, landing angle, …). For COURSE_PLAY: the scorecard with per-hole scores and per-shot metrics.

NameTypeReqDescription
activity_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

list_sessions ~85

List the player's activities (practice sessions and course rounds).

NameTypeReqDescription
include_hiddenbooleaninclude activities the user has hidden.
kindsoptional ActivityKind filter, e.g. ["RANGE_PRACTICE", "COURSE_PLAY"].
skipinteger
takeinteger
time_from
time_to

Structured output declared, but exposes no named fields.

No examples provided.

session_analysis ~135

Per-session analysis (deterministic classification + metrics, stored locally). Actions: - `analyze` (needs `activity_id`): fetch a session, classify it (warm-up vs serious practice vs game), compute metrics, normalize vs prior stored sessions, store the record (last 30 kept), and return it. - `get` (needs `activity_id`): return one stored analysis record. - `list`: return the index of stored analyses (most recent first). Drive this with the `trackman-session-analyzer` prompt.

NameTypeReqDescription
actionstringyes
activity_id

Structured output declared, but exposes no named fields.

No examples provided.

setup ~160

One-call onboarding for the Trackman golf coach. Returns everything needed to set the coach up in your client: - `system_prompt`: paste into a Claude/ChatGPT **Project's** custom instructions so every chat in it is the coach (with this MCP connected); - `skills`: upload-ready `SKILL.md` files (Settings → Capabilities → Skills) for always-on auto-activation; - `instructions`: per-client steps (Claude Projects, Desktop Skills, ChatGPT, Claude Code). An MCP server can't create the Project or enable Skills itself — this hands you the content + steps. In Claude Code, the assistant can write the files for you directly from this kit. (Pairs with the `setup` prompt.)

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

training_plan ~294

The coach's memory: save prescribed practice plans and recall/grade them. Actions: - `save` (needs `plan`): persist a prescribed plan to the pending queue. The `plan` is a structured dict — title, focus, diagnosis, blocks [{name, club, reps, detail, link, goal}], and optional `target_specs` (machine-readable targets, e.g. {metric:'clubPath', club:'DRIVER', op:'between', low:-1, high:2}) used by `verify`. Returns the stored plan (with id). Capped at the most recent 50. - `next`: return the next pending plan — the answer to "what's today's training?". - `list` (optional `status`='pending'|'done'): list plans, oldest→newest. - `done` (needs `plan_id`, optional `result_session_id`): mark a plan complete. - `verify` (needs `plan_id`, optional `activity_id`): grade a recent session's real shot metrics against the plan's `target_specs`; returns per-target session-mean vs target, `all_met`, and a recommendation.

NameTypeReqDescription
actionstringyes
activity_id
plan
plan_id
result_session_id
status

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the io.github.bjornj12/trackman-mcp server?

io.github.bjornj12/trackman-mcp is listed in the public MCP registry as io.github.bjornj12/trackman-mcp. Fetch your Trackman Golf stats (handicap, rounds, shots, club gapping) as MCP tools. This page covers its PyPI package (trackman-mcp).

Is the io.github.bjornj12/trackman-mcp server safe to use?

io.github.bjornj12/trackman-mcp scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 13 September 2026. 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 io.github.bjornj12/trackman-mcp server expose?

io.github.bjornj12/trackman-mcp exposes 12 tools: auth, get_profile, get_handicap, list_sessions, get_session, and 7 more. Their descriptions and schemas cost roughly 1,386 tokens of context every time the server is loaded.

Is the io.github.bjornj12/trackman-mcp server still maintained?

io.github.bjornj12/trackman-mcp is still listed as active in the MCP registry. We last reached this channel on 13 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.