SisRUN Training Plan
PYPI · SISRUN-MCP · SCANNED SEP 20
Read your SisRUN (appsisrun.com.br) training plan: prescribed workouts, pace/HR windows, structure
Available components
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 27 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
{
"mcpServers": {
"cdutr-sisrun-mcp": {
"command": "uvx",
"args": [
"sisrun-mcp"
]
}
}
} {
"servers": {
"cdutr-sisrun-mcp": {
"command": "uvx",
"args": [
"sisrun-mcp"
]
}
}
} codex mcp add cdutr-sisrun-mcp -- uvx sisrun-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cdutr-sisrun-mcp": {
"type": "local",
"command": [
"uvx",
"sisrun-mcp"
],
"enabled": true
}
}
} openclaw mcp add cdutr-sisrun-mcp --command uvx --arg sisrun-mcp
mcp_servers:
cdutr-sisrun-mcp:
command: "uvx"
args: ["sisrun-mcp"] {
"McpServers": {
"cdutr-sisrun-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"sisrun-mcp"
]
}
}
} assistant mcp add cdutr-sisrun-mcp -t stdio -c uvx -a sisrun-mcp
{
"mcpServers": {
"cdutr-sisrun-mcp": {
"command": "uvx",
"args": [
"sisrun-mcp"
]
}
}
} 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 Sept 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.
- 18 Sept 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.
- 15 Sept 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 Sept 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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 5 Sept 26 +16
- Malware scan: unverified → pass ▲ security
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 20 Sept 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 |
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 →
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.
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.