Kilter Board Logbook
PYPI · KILTER-MCP
Read-only access to your Kilter Board logbook: sessions, sends, projects and grade stats
Available components
Last scanned (16 hours ago)
Scores higher than 80% 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 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 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/kilter-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 63 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1294 tokens (~143/item across 9 items; 9 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 (15)
- 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
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
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.
- 20 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 16 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Analysed pypi/kilter-mcp@0.2.2
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/kilter-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/wmmg101/kilter-mcp/.github/workflows/release.yml@refs/tags/v0.2.2 |
| Rekor log index | 2884021507 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:dd21b8e992a8f1a90cb275b9b267e6f109495f18ff84347140547a60fa3116b0 |
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 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 →
kilter_get_angle_stats ~82
Return per-wall-angle statistics so angles can be compared. Use when the user asks to compare angles (e.g. 20° vs 40°), which angle they climb hardest or most at, or flash rate by angle. One row per angle with sends, flashes, attempts, sessions, hardest send/flash and sends per grade.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
kilter_get_grade_pyramid ~90
Return the user's send pyramid: sends per grade, hardest first, with flash rates. Use when the user asks about their grade pyramid, distribution of grades, flash rate per grade, or how solid they are at a level. Optional wall-angle filter.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | – | – | Wall angle in degrees (e.g. 20, 30, 40). Omit for all angles. |
Structured output declared, but exposes no named fields.
No examples provided.
kilter_get_hardest_sends ~101
Return the user's hardest sent climbs (unique per climb and angle), hardest first. Use when the user asks about their hardest sends, best climbs, max grade, or personal bests. Optional wall-angle filter; limit defaults to 10.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | – | – | Wall angle in degrees (e.g. 20, 30, 40). Omit for all angles. |
| limit | – | – | Maximum number of items to return. |
Structured output declared, but exposes no named fields.
No examples provided.
kilter_get_logs ~203
Return the user's Kilter logbook entries, newest first. Use when the user asks about recent Kilter climbs, attempts, what they climbed on a date, or wants raw history. Each entry is one climb at one wall angle on one date with the number of tries in that entry. Filters: limit (default 25, max 500), angle (degrees), topped (true=only sends, false=only unsuccessful attempts), start_date/end_date (YYYY-MM-DD, inclusive).
| Name | Type | Req | Description |
|---|---|---|---|
| angle | – | – | Wall angle in degrees (e.g. 20, 30, 40). Omit for all angles. |
| 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. |
| topped | – | – | true = only topped (sent) entries, false = only unsuccessful attempts. |
Structured output declared, but exposes no named fields.
No examples provided.
kilter_get_progression ~131
Return climbing progression over time, oldest period first. Use when the user asks how they have progressed, trends, whether they are improving, or for a month-by-month/week-by-week view. period is 'month' (default) or 'week'. Each period has sessions, sends, unique climbs, flashes, attempts and hardest send/flash. Optional wall-angle filter.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | – | – | Wall angle in degrees (e.g. 20, 30, 40). Omit for all angles. |
| period | string | – | Bucket size for the progression: calendar month or ISO week. |
Structured output declared, but exposes no named fields.
No examples provided.
kilter_get_projects ~121
Return the user's projects: climbs attempted but never topped at that wall angle. Use when the user asks what they are working on, unfinished climbs, or what to try next. A climb is a project per (climb, angle); sending it at another angle does not remove it. Sorted by most recently tried, then most attempts. Optional angle filter.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | – | – | Wall angle in degrees (e.g. 20, 30, 40). Omit for all angles. |
| limit | – | – | Maximum number of items to return. |
Structured output declared, but exposes no named fields.
No examples provided.
kilter_get_sends ~151
Return climbs the user has topped (sent), newest first. Use when the user asks about their sends, ticks, completed climbs or flashes. Entries with status 'flash' were topped on the first try. Filters: limit (default 25, max 500), angle (degrees), start_date/end_date (YYYY-MM-DD).
| Name | Type | Req | Description |
|---|---|---|---|
| angle | – | – | Wall angle in degrees (e.g. 20, 30, 40). Omit for all angles. |
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
kilter_get_sessions ~86
Return recent climbing sessions (entries grouped by calendar day), newest first. Use when the user asks how their last session went, what they climbed yesterday, or wants to compare sessions. Each session lists angles, sends, flashes, attempts, hardest send and every climb logged that day. limit defaults to 5.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | Maximum number of items to return. |
Structured output declared, but exposes no named fields.
No examples provided.
kilter_get_summary ~80
Return a compact overview of the user's whole Kilter history. Use first when the user asks a broad question ("how is my climbing going?", "summarise my Kilter account") or when you need totals: entries, sends, flashes, attempts, angles climbed, date range, session count, hardest send/flash and sends per grade.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Kilter Board Logbook MCP server?
Kilter Board Logbook runs locally as a PyPI package, launched with uvx kilter-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 · kilter-mcp
claude mcp add wmmg101-kilter-mcp -- uvx kilter-mcp
What is the Kilter Board Logbook MCP server?
Kilter Board Logbook is an MCP server listed in the public MCP registry as io.github.wmmg101/kilter-mcp. Read-only access to your Kilter Board logbook: sessions, sends, projects and grade stats. This page covers its PyPI package (kilter-mcp).
Is the Kilter Board Logbook MCP server safe to use?
Kilter Board Logbook scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 Kilter Board Logbook MCP server expose?
Kilter Board Logbook exposes 9 tools: kilter_get_logs, kilter_get_sends, kilter_get_projects, kilter_get_summary, kilter_get_grade_pyramid, and 4 more. Their descriptions and schemas cost roughly 1,045 tokens of context every time the server is loaded.
Is the Kilter Board Logbook MCP server still maintained?
Kilter Board Logbook is still listed as active in the MCP registry. We last reached this channel on 21 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 Kilter Board Logbook MCP server under?
Kilter Board 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.
What did VerifyMCP test on the Kilter Board Logbook MCP server?
VerifyMCP ran 15 checks on Kilter Board Logbook, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Kilter Board Logbook: Malware scan. 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.