Boardsesh Climbing Logbook
PYPI · BOARDSESH-MCP
Read-only access to your Boardsesh logbook across Kilter, Tension, MoonBoard and more
Available components
Last scanned (1 hour ago)
Scores higher than 95% 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 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to wmmg101/boardsesh-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 24 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2132 tokens (~177/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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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
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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 47 to 67. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 47. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 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.
- 30 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 28 Sept 26 +11
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +2
- License: fail → pass ▲ functional
- Licence: MIT functional
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 17 Oct 2026 · Analysed pypi/boardsesh-mcp@0.1.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 | wmmg101/boardsesh-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/wmmg101/boardsesh-mcp/.github/workflows/release.yml@refs/tags/v0.1.0 |
| Rekor log index | 2909706056 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:ad2df5f32f2146c3db1b7c9eb1cdac8edd81d012e0e78d6da579a31d69d24c07 |
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 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 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 →
boardsesh_compare_boards ~111
Compare the user's climbing across every board they have logged on. Use when the user asks which board they are strongest on, how Kilter compares with Tension or MoonBoard, or where they climb most. One row per board with sends, flashes, flash rate, tries, sessions, angles, hardest send in that board's own grades, and 'hardest_boardsesh_grade' / 'median_boardsesh_grade' which are normalised across boards and therefore the fair comparison.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
boardsesh_find_similar_climbs ~192
Find climbs that use a similar set of holds to a given climb. Use when the user asks for climbs like one they enjoyed or one they are projecting, or wants to train a specific movement again. Similarity is hold overlap (0-1); 0.5 and above feels genuinely related. Pass a climb_uuid from an earlier result.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | – | – | Wall angle in degrees (e.g. 20, 40). Omit for all angles. |
| board | – | – | Board type to filter to: kilter, tension, moonboard, decoy, touchstone, soill, grasshopper, woods or spray. Omit for all boards. |
| climb_uuid | string | yes | The climb to match, as a climb_uuid from another tool's output (e.g. a send or project). |
| limit | – | – | Maximum number of items to return. |
Structured output declared, but exposes no named fields.
No examples provided.
boardsesh_get_ascents ~239
Return the user's logbook entries, newest first, across every board. Use when the user asks about recent climbs, sends, flashes, attempts, what they did on a date, or wants raw history. Each entry is one climb at one angle on one board at one time with the number of tries. Filters: limit (default 25), board, angle, status ('all', 'sends', 'attempts', 'flashes'), start_date/end_date (YYYY-MM-DD).
| Name | Type | Req | Description |
|---|---|---|---|
| angle | – | – | Wall angle in degrees (e.g. 20, 40). Omit for all angles. |
| board | – | – | Board type to filter to: kilter, tension, moonboard, decoy, touchstone, soill, grasshopper, woods or spray. Omit for all boards. |
| end_date | – | – | Inclusive end date, YYYY-MM-DD, in the user's timezone. |
| limit | – | – | Maximum number of items to return. |
| start_date | – | – | Inclusive start date, YYYY-MM-DD, in the user's timezone. |
| status | – | – | Filter by outcome. 'sends' includes flashes. |
Structured output declared, but exposes no named fields.
No examples provided.
boardsesh_get_grade_pyramid ~118
Return the user's send pyramid: sends per grade, hardest first, with flash rates. Use when the user asks about their pyramid, grade distribution, flash rate per grade, or how solid they are at a level. Optional board filter; grades differ between boards, so prefer filtering to one board when the user names one.
| Name | Type | Req | Description |
|---|---|---|---|
| board | – | – | Board type to filter to: kilter, tension, moonboard, decoy, touchstone, soill, grasshopper, woods or spray. Omit for all boards. |
Structured output declared, but exposes no named fields.
No examples provided.
boardsesh_get_grades ~87
Return a board's grade scale: difficulty_id to grade label. Use when you need a difficulty_id for a grade the user named (e.g. to pass min_grade_id to a search), or to explain what a grade id means. Boards do not share one scale.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | Board type, e.g. kilter, tension, moonboard. |
Structured output declared, but exposes no named fields.
No examples provided.
boardsesh_get_hold_heatmap ~254
Return which holds the wall's climbs use, for spotting strengths and weaknesses. Use when the user asks about weaknesses, hold types they avoid or overuse, or what to train. Returns per-hold counts (how many climbs use each hold, and whether as hand, foot, start or finish) plus the average difficulty of climbs using it. Combine with a grade range to ask "which holds appear in climbs at my next grade". Hold ids are wall positions; reason about patterns and grade ranges rather than individual ids.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | – | – | Wall angle in degrees (e.g. 20, 40). Omit for all angles. |
| board | – | – | Board type to filter to: kilter, tension, moonboard, decoy, touchstone, soill, grasshopper, woods or spray. Omit for all boards. |
| limit | – | – | Maximum number of items to return. |
| max_grade_id | – | – | Only count climbs at or below this difficulty_id. |
| min_grade_id | – | – | Only count climbs at or above this difficulty_id. |
| only_my_projects | – | – | Restrict to climbs the user has attempted but not completed, to see which holds show up in their unfinished projects. |
Structured output declared, but exposes no named fields.
No examples provided.
boardsesh_get_progression ~131
Return climbing progression over time, oldest period first. Use when the user asks whether they are improving, about trends, or for a month-by-month or week-by-week view. Each period has sessions, boards used, entries, sends, unique climbs, flashes, tries and the hardest send.
| Name | Type | Req | Description |
|---|---|---|---|
| board | – | – | Board type to filter to: kilter, tension, moonboard, decoy, touchstone, soill, grasshopper, woods or spray. Omit for all boards. |
| period | string | – | Bucket size for the progression: calendar month or ISO week. |
Structured output declared, but exposes no named fields.
No examples provided.
boardsesh_get_projects ~129
Return the user's projects: climbs attempted but never sent at that angle. Use when the user asks what they are working on, unfinished climbs, or what to try again. A project is per (board, climb, angle), so sending a climb at another angle does not remove it. Sorted by most recently tried, then most tries.
| Name | Type | Req | Description |
|---|---|---|---|
| board | – | – | Board type to filter to: kilter, tension, moonboard, decoy, touchstone, soill, grasshopper, woods or spray. Omit for all boards. |
| limit | – | – | Maximum number of items to return. |
Structured output declared, but exposes no named fields.
No examples provided.
boardsesh_get_sessions ~126
Return recent climbing sessions (entries grouped by calendar day), newest first. Use when the user asks how their last session went, what they climbed on a day, or wants to compare sessions. Each session lists the boards and angles used, sends, flashes, total tries, hardest send and every climb logged that day.
| Name | Type | Req | Description |
|---|---|---|---|
| board | – | – | Board type to filter to: kilter, tension, moonboard, decoy, touchstone, soill, grasshopper, woods or spray. Omit for all boards. |
| limit | – | – | Maximum number of items to return. |
Structured output declared, but exposes no named fields.
No examples provided.
boardsesh_get_summary ~82
Return a compact overview of the user's whole Boardsesh history, across all boards. Use first for broad questions ("how is my climbing going?", "summarise my logbook") or when you need totals: entries, sends, flashes, tries, boards used, angles, date range, session count, hardest send and flash, and sends per grade.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
boardsesh_recommend_climbs ~209
Suggest climbs the user has not sent yet, from Boardsesh's recommendations. Use when the user asks what to try next, wants new climbs, projects at their level, or something fresh. 'at_level' works from their own send history and excludes climbs they have already sent. Needs a board configuration, so it uses one of the user's saved Boardsesh boards.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | – | – | Wall angle in degrees (e.g. 20, 40). Omit for all angles. |
| board | – | – | Board type to filter to: kilter, tension, moonboard, decoy, touchstone, soill, grasshopper, woods or spray. Omit for all boards. |
| kind | string | – | 'at_level' picks climbs around the user's current grade, 'crowd_favorites' popular ones, 'hidden_gems' under-climbed ones, 'fresh' recently set ones. |
| limit | – | – | Maximum number of items to return. |
Structured output declared, but exposes no named fields.
No examples provided.
boardsesh_search_climbs ~234
Search the board's climb catalogue with filters. Use when the user wants to find specific climbs: by name, grade range, benchmarks only, popularity, or excluding ones they have already sent. For "what should I try next" prefer boardsesh_recommend_climbs, which uses the user's own level.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | – | – | Wall angle in degrees (e.g. 20, 40). Omit for all angles. |
| board | – | – | Board type to filter to: kilter, tension, moonboard, decoy, touchstone, soill, grasshopper, woods or spray. Omit for all boards. |
| exclude_sent | – | – | Hide climbs the user has already sent at this angle. |
| limit | – | – | Maximum number of items to return. |
| max_grade_id | – | – | Maximum difficulty_id. |
| min_ascents | – | – | Only climbs with at least this many community ascents. |
| min_grade_id | – | – | Minimum difficulty_id (see boardsesh_get_grades). |
| name | – | – | Match part of a climb name. |
| only_benchmarks | – | – | Only benchmark climbs. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Boardsesh Climbing Logbook MCP server?
Boardsesh Climbing Logbook runs locally as a PyPI package, launched with uvx boardsesh-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 · boardsesh-mcp
claude mcp add wmmg101-boardsesh-mcp -- uvx boardsesh-mcp
What is the Boardsesh Climbing Logbook MCP server?
Boardsesh Climbing Logbook is an MCP server listed in the public MCP registry as io.github.wmmg101/boardsesh-mcp. Read-only access to your Boardsesh logbook across Kilter, Tension, MoonBoard and more. This page covers its PyPI package (boardsesh-mcp).
Is the Boardsesh Climbing Logbook MCP server safe to use?
Boardsesh Climbing Logbook scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 Boardsesh Climbing Logbook MCP server expose?
Boardsesh Climbing Logbook exposes 12 tools: boardsesh_get_summary, boardsesh_get_ascents, boardsesh_get_sessions, boardsesh_get_projects, boardsesh_compare_boards, and 7 more. Their descriptions and schemas cost roughly 1,912 tokens of context every time the server is loaded.
Is the Boardsesh Climbing Logbook MCP server still maintained?
Boardsesh Climbing Logbook is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Boardsesh Climbing Logbook MCP server under?
Boardsesh Climbing Logbook declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.