# SisRUN Training Plan (pypi · sisrun-mcp)

Read your SisRUN (appsisrun.com.br) training plan: prescribed workouts, pace/HR windows, structure

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `sisrun-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/cdutr-sisrun-mcp/sisrun-mcp.md), [page](https://verifymcp.io/servers/cdutr-sisrun-mcp/sisrun-mcp)

## Channel facts

- Registry: `pypi`
- Package: `sisrun-mcp`
- Version: `0.1.0`
- 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-20.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - 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 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/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 27 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 187 tokens (~62/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 SisRUN Training Plan MCP server?

SisRUN Training Plan runs locally as a PyPI package, launched with uvx sisrun-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 cdutr-sisrun-mcp -- uvx sisrun-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cdutr-sisrun-mcp": {
      "command": "uvx",
      "args": [
        "sisrun-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cdutr-sisrun-mcp": {
      "command": "uvx",
      "args": [
        "sisrun-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cdutr-sisrun-mcp -- uvx sisrun-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add cdutr-sisrun-mcp --command uvx --arg sisrun-mcp
```

### Hermes

```yaml
mcp_servers:
  cdutr-sisrun-mcp:
    command: "uvx"
    args: ["sisrun-mcp"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add cdutr-sisrun-mcp -t stdio -c uvx -a sisrun-mcp
```

### Other

```json
{
  "mcpServers": {
    "cdutr-sisrun-mcp": {
      "command": "uvx",
      "args": [
        "sisrun-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 64, +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.

### 2026-09-18 (score 63, +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.

### 2026-09-15 (score 62, +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.

### 2026-09-13 (score 61, +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.

### 2026-09-11 (score 60, +1)

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

### 2026-09-09 (score 59, +1)

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

### 2026-09-07 (score 58, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-05 (score 72, +16)

- [security improvement] Malware scan: unverified → pass

## MCP tools (3)

### `get_current_week` (~91 tokens)

The current week's training plan: every workout with status (Proposto =
prescribed / Feito = done / Feito Avulso = auto-imported, not prescribed),
modality, prescribed distance (planned_km is the honest number; the raw
distance_km field is blank on interval days), pace/HR windows, the coach's
structured session, and what SisRUN matched as delivered.

Output parameters:

- `result` (string)

### `get_week` (~44 tokens)

The training plan for the week containing `date` (YYYY-MM-DD).
Navigating far from the current week costs one request per week hop.

Input parameters:

- `date` (string, required)

Output parameters:

- `result` (string)

### `get_upcoming` (~52 tokens)

Prescribed workouts (status Proposto) from today forward, across the
current week plus `weeks_ahead` future weeks (default 1, max 8).

Input parameters:

- `weeks_ahead` (integer)

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-09-20: 64
- 2026-09-19: 63
- 2026-09-18: 63
- 2026-09-17: 62
- 2026-09-16: 62
- 2026-09-15: 62
- 2026-09-14: 61
- 2026-09-13: 61
- 2026-09-12: 60
- 2026-09-11: 60
- 2026-09-10: 59
- 2026-09-09: 59
- 2026-09-08: 58
- 2026-09-07: 58
- 2026-09-06: 72
- 2026-09-05: 72
- 2026-09-04: 56
- 2026-09-03: 56
- 2026-09-02: 55
- 2026-09-01: 55
- 2026-08-31: 70
- 2026-08-30: 66
- 2026-08-29: 51
- 2026-08-28: 51
- 2026-08-27: 51
- 2026-08-26: 66
- 2026-08-25: 49
- 2026-08-24: 49
- 2026-08-23: 49

## Common questions

### What is the SisRUN Training Plan MCP server?

SisRUN Training Plan is an MCP server listed in the public MCP registry as io.github.cdutr/sisrun-mcp. Read your SisRUN (appsisrun.com.br) training plan: prescribed workouts, pace/HR windows, structure. This page covers its PyPI package (sisrun-mcp).

### Is the SisRUN Training Plan MCP server safe to use?

SisRUN Training Plan scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 SisRUN Training Plan MCP server expose?

SisRUN Training Plan exposes 3 tools: get_current_week, get_week, get_upcoming. Their descriptions and schemas cost roughly 187 tokens of context every time the server is loaded.

### Is the SisRUN Training Plan MCP server still maintained?

SisRUN Training Plan is still listed as active in the MCP registry. We last reached this channel on 20 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/sisrun-mcp/
- Socket report: https://socket.dev/pypi/package/sisrun-mcp
- Repository: https://github.com/cdutr/sisrun-mcp
- Changelog RSS feed: https://verifymcp.io/servers/cdutr-sisrun-mcp/sisrun-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cdutr-sisrun-mcp/sisrun-mcp.json
- HTML version of this page: https://verifymcp.io/servers/cdutr-sisrun-mcp/sisrun-mcp