io.github.bjornj12/trackman-mcp
PYPI · TRACKMAN-MCP
Fetch your Trackman Golf stats (handicap, rounds, shots, club gapping) as MCP tools.
Available components
Last scanned (12 hours ago)
Scores higher than 90% of PyPI servers
Category Entertainment and Games
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to bjornj12/trackman-mcp-client). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 125 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management80
- Stability observed for 24 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 5 Nov 26 −2
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
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 · Analysed pypi/trackman-mcp@0.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | bjornj12/trackman-mcp-client |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/bjornj12/trackman-mcp-client/.github/workflows/publish.yml@refs/tags/v0.4.0 |
| Rekor log index | 2047479549 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:bcab83ae9638be2af42df7e7e54099131db47394965498c6841174b48a04d717 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
auth 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| open_browser | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
build_visualization 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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_activity_summary Get Activity Summary ~47
Get activity counts grouped by kind over an optional time window.
| Name | Type | Req | Description |
|---|---|---|---|
| skip | integer | – | – |
| take | integer | – | – |
| time_from | – | – | – |
| time_to | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_club_stats 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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_retired | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_course_rounds 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).
| Name | Type | Req | Description |
|---|---|---|---|
| completed | – | – | filter by completion (True = finished rounds only). |
| skip | integer | – | – |
| take | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_handicap Get Handicap ~60
Get handicap history: per-round differentials and how the index moved.
| Name | Type | Req | Description |
|---|---|---|---|
| only_in_avg | boolean | – | only records counted in the handicap average. |
| skip | integer | – | paging offset. |
| take | integer | – | number of records to return. |
Structured output declared, but exposes no named fields.
No examples provided.
get_profile 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_sessions List Sessions ~85
List the player's activities (practice sessions and course rounds).
| Name | Type | Req | Description |
|---|---|---|---|
| include_hidden | boolean | – | include activities the user has hidden. |
| kinds | – | – | optional ActivityKind filter, e.g. ["RANGE_PRACTICE", "COURSE_PLAY"]. |
| skip | integer | – | – |
| take | integer | – | – |
| time_from | – | – | – |
| time_to | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
session_analysis 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| activity_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
setup 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| activity_id | – | – | – |
| plan | – | – | – |
| plan_id | – | – | – |
| result_session_id | – | – | – |
| status | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
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
claude mcp add bjornj12-trackman-mcp -- uvx trackman-mcp
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 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.bjornj12/trackman-mcp server under?
io.github.bjornj12/trackman-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.bjornj12/trackman-mcp server?
VerifyMCP ran 16 checks on io.github.bjornj12/trackman-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.