io.github.joeyaflores/ourpr-mcp-server
NPM · OURPR-MCP-SERVER
Read your own ourpr running history in an AI agent, and put a plan on the week ahead.
Available components
Last scanned (22 hours ago)
Scores higher than 98% of npm 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
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to joeyaflores/ourpr-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 49 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1005 tokens (~91/item across 11 items; 11 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 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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 (16)
- Malware scan
- 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
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 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.
- 7 Nov 26 −3
- Stability: pass → 0.83 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 24 Oct 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.
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 npm/ourpr-mcp-server@0.5.0
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | joeyaflores/ourpr-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/joeyaflores/ourpr-mcp-server/.github/workflows/publish.yml@refs/tags/v0.5.0 |
| Rekor log index | 3055789138 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6feebfdb131c05eb639eb0c43b6aba4f83860da6a9f2f03b14eb0645fa5f446da1808db0986648a3e9c2892cc25622de8a67efab5407f548c0ec17885 |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
ourpr_detect_reps Look for reps in one run ~39
Whether one particular run was an interval session, and its reps.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | Run id from ourpr_list_runs. |
| Name | Type | Req | Description |
|---|---|---|---|
| detection | object | yes | – |
No examples provided.
ourpr_get_run Get one run in full ~63
One activity in full: mile splits with heart rate, cadence, calories, device. Id comes from ourpr_list_runs. For the profile along the route, use ourpr_run_stream.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | Run id from ourpr_list_runs. |
| Name | Type | Req | Description |
|---|---|---|---|
| run | object | yes | – |
| splits | array | yes | – |
No examples provided.
ourpr_list_plans List planned runs in a date range ~111
The runner's planned runs between two dates: day, name, miles, time, tag, the runner's note, whether a logged run fulfilled it, and whether ourpr create wrote it. Read it before ourpr_plan_week so a new plan does not land on a day that already holds one.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | Last day, YYYY-MM-DD. Default 13 days after the first. |
| start_date | string | – | First day, YYYY-MM-DD. Default today. |
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| plans | array | yes | – |
| start_date | string | yes | – |
| truncated | boolean | yes | – |
No examples provided.
ourpr_list_races List the races in the history ~83
Every race ourpr finds in the history, newest first, tune-ups included: date, name, distance, time, pace and run id. Also the fastest result at 5K, 10K, half marathon and marathon among them.
| Name | Type | Req | Description |
|---|---|---|---|
| distance | string | – | Only races at this distance. |
| limit | integer | – | Most rows to return. |
| Name | Type | Req | Description |
|---|---|---|---|
| fastest | array | yes | – |
| races | array | yes | – |
| returned | number | yes | – |
| total | number | yes | – |
No examples provided.
ourpr_list_runs List runs in a date range ~183
Training history between two dates, newest first: date, local start, name, type, miles, pace, time, elevation, average heart rate, and on a runs-only list Friel's efficiency factor and the heartbeats each mile took. Start here for totals, streaks, trends, or finding a run. For one run's splits, use ourpr_get_run with an id from here.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Last day to include, YYYY-MM-DD. Example: 2026-06-30 |
| include_non_runs | boolean | – | Include rides, gym and other types. Runs only by default. |
| limit | integer | – | Most rows to return. The answer says what it left out. |
| start_date | string | yes | First day to include, YYYY-MM-DD. Example: 2026-01-01 |
| Name | Type | Req | Description |
|---|---|---|---|
| returned | number | yes | – |
| runs | array | yes | – |
| total_in_window | number | yes | – |
| truncated | boolean | yes | – |
No examples provided.
ourpr_plan_week Put runs on the runner's week ~76
Write one planned run, or a week of them, onto days still ahead. Each lands on the runner's week as a plan they can see, edit and remove. Needs a token made with the write scope and ourpr create. Never logs a run.
| Name | Type | Req | Description |
|---|---|---|---|
| plans | array | yes | One run, or up to fourteen. |
| Name | Type | Req | Description |
|---|---|---|---|
| written | array | yes | – |
No examples provided.
ourpr_rep_workouts Find rep workouts across the history ~53
Interval sessions found across the history, with reps and distances. Detection is conservative, so a session it misses is still in ourpr_list_runs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many recent activities to read. |
| Name | Type | Req | Description |
|---|---|---|---|
| scanned | number | yes | – |
| workouts | array | yes | – |
No examples provided.
ourpr_run_laps Get a run's laps ~54
The laps the watch recorded for one run — the runner's own button presses. Laps follow the workout; mile splits follow the mile.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | Run id from ourpr_list_runs. |
| Name | Type | Req | Description |
|---|---|---|---|
| laps | array | yes | – |
No examples provided.
ourpr_run_stream Get a run's elevation and sensor profile ~103
A run's profile on a 10 m grid — elevation, heart rate, power, cadence — as min, average, max and coverage per channel, not every sample. Also each half by distance with its moving pace, heart rate and efficiency, and the drift between them (aerobic decoupling, Pa:HR). No profile is a normal answer for an indoor run.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | Run id from ourpr_list_runs. |
| Name | Type | Req | Description |
|---|---|---|---|
| channels | object | yes | – |
| grid_m | number | yes | – |
| halves | – | yes | – |
| samples | number | yes | – |
| total_miles | number | yes | – |
No examples provided.
ourpr_similar_terrain Find runs over comparable ground ~86
Stretches of past runs matching a distance and climb — what the runner has already done that resembles a race they are training for.
| Name | Type | Req | Description |
|---|---|---|---|
| gain_ft | number | yes | Target climb in feet. |
| limit | integer | – | How many to return. |
| miles | number | yes | Target distance in miles. |
| tolerance_ft | number | – | Climb tolerance, feet. |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | yes | – |
| scanned | number | yes | – |
No examples provided.
ourpr_training_blocks Get the goal race and training blocks ~89
The goal race and its Block: race day, distance, goal time, which week of the Block today falls in, and miles for each week. Also the Blocks before past races, each with its result, weeks and peak week. A Block is the race-anchored Monday to Sunday weeks before a race.
| Name | Type | Req | Description |
|---|---|---|---|
| past | integer | – | How many past Blocks to include, newest first. |
| Name | Type | Req | Description |
|---|---|---|---|
| goal | – | yes | – |
| past | array | yes | – |
| total_races | number | yes | – |
No examples provided.
How do I install the io.github.joeyaflores/ourpr-mcp-server server?
io.github.joeyaflores/ourpr-mcp-server runs locally as an npm package, launched with npx -y ourpr-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ourpr-mcp-server
claude mcp add joeyaflores-ourpr-mcp-server -- npx -y ourpr-mcp-server
What is the io.github.joeyaflores/ourpr-mcp-server server?
io.github.joeyaflores/ourpr-mcp-server is listed in the public MCP registry as io.github.joeyaflores/ourpr-mcp-server. Read your own ourpr running history in an AI agent, and put a plan on the week ahead. This page covers its npm package (ourpr-mcp-server).
Is the io.github.joeyaflores/ourpr-mcp-server server safe to use?
io.github.joeyaflores/ourpr-mcp-server scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.joeyaflores/ourpr-mcp-server server expose?
io.github.joeyaflores/ourpr-mcp-server exposes 11 tools: ourpr_list_runs, ourpr_get_run, ourpr_run_stream, ourpr_run_laps, ourpr_rep_workouts, and 6 more. Their descriptions and schemas cost roughly 940 tokens of context every time the server is loaded.
Is the io.github.joeyaflores/ourpr-mcp-server server still maintained?
io.github.joeyaflores/ourpr-mcp-server 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 io.github.joeyaflores/ourpr-mcp-server server under?
io.github.joeyaflores/ourpr-mcp-server 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 io.github.joeyaflores/ourpr-mcp-server server?
VerifyMCP ran 16 checks on io.github.joeyaflores/ourpr-mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.