SisRUN Training Plan
PYPI · SISRUN-MCP
Read your SisRUN (appsisrun.com.br) training plan: prescribed workouts, pace/HR windows, structure
Available components
Last scanned (11 hours ago)
Scores higher than 85% of PyPI servers
Category Health and Science
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 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 73 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 187 tokens (~62/item across 3 items; 3 tools + 0 resources), lean.Pass
- 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 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 5 Nov 2026 · Analysed pypi/sisrun-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 28 packages
| Packages resolved | 28 |
|---|---|
| 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 →
get_current_week ~91
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_upcoming ~52
Prescribed workouts (status Proposto) from today forward, across the current week plus `weeks_ahead` future weeks (default 1, max 8).
| Name | Type | Req | Description |
|---|---|---|---|
| weeks_ahead | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_week ~44
The training plan for the week containing `date` (YYYY-MM-DD). Navigating far from the current week costs one request per week hop.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.
pypi · sisrun-mcp
claude mcp add cdutr-sisrun-mcp -- uvx sisrun-mcp
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 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 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 SisRUN Training Plan MCP server under?
SisRUN Training Plan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.