# Kilter Board Logbook (pypi · kilter-mcp)

Read-only access to your Kilter Board logbook: sessions, sends, projects and grade stats

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `kilter-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/wmmg101-kilter-mcp/kilter-mcp.md), [page](https://verifymcp.io/servers/wmmg101-kilter-mcp/kilter-mcp)

## Channel facts

- Registry: `pypi`
- Package: `kilter-mcp`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 30 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add wmmg101-kilter-mcp -- uvx kilter-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "wmmg101-kilter-mcp": {
      "command": "uvx",
      "args": [
        "kilter-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wmmg101-kilter-mcp": {
      "command": "uvx",
      "args": [
        "kilter-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wmmg101-kilter-mcp -- uvx kilter-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wmmg101-kilter-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "kilter-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wmmg101-kilter-mcp --command uvx --arg kilter-mcp
```

### Hermes

```yaml
mcp_servers:
  wmmg101-kilter-mcp:
    command: "uvx"
    args: ["kilter-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "wmmg101-kilter-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "kilter-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add wmmg101-kilter-mcp -t stdio -c uvx -a kilter-mcp
```

### Other

```json
{
  "mcpServers": {
    "wmmg101-kilter-mcp": {
      "command": "uvx",
      "args": [
        "kilter-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 71, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-18 (score 55, −12)

- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 0.2.1 → 0.2.2

### 2026-09-16 (score 67)

First indexed and scored.

## MCP tools (9)

### `kilter_get_logs` (~203 tokens)

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

Input parameters:

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

### `kilter_get_sends` (~151 tokens)

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

Input parameters:

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

### `kilter_get_projects` (~121 tokens)

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.

Input parameters:

- `angle`: Wall angle in degrees (e.g. 20, 30, 40). Omit for all angles.
- `limit`: Maximum number of items to return.

### `kilter_get_summary` (~80 tokens)

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.

### `kilter_get_grade_pyramid` (~90 tokens)

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.

Input parameters:

- `angle`: Wall angle in degrees (e.g. 20, 30, 40). Omit for all angles.

### `kilter_get_hardest_sends` (~101 tokens)

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.

Input parameters:

- `angle`: Wall angle in degrees (e.g. 20, 30, 40). Omit for all angles.
- `limit`: Maximum number of items to return.

### `kilter_get_sessions` (~86 tokens)

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.

Input parameters:

- `limit`: Maximum number of items to return.

### `kilter_get_progression` (~131 tokens)

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.

Input parameters:

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

### `kilter_get_angle_stats` (~82 tokens)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/wmmg101-kilter-mcp/kilter-mcp#diagnostics

## Score history

- 2026-09-21: 71
- 2026-09-20: 71
- 2026-09-19: 55
- 2026-09-18: 55
- 2026-09-17: 67
- 2026-09-16: 67

## Common questions

### 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 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 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 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/kilter-mcp/
- Socket report: https://socket.dev/pypi/package/kilter-mcp
- Repository: https://github.com/wmmg101/kilter-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wmmg101-kilter-mcp/kilter-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wmmg101-kilter-mcp/kilter-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wmmg101-kilter-mcp/kilter-mcp