# ourpr-mcp-server

MCP server for your own ourpr running history: read it, and put a plan on the week ahead

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.4.1
- **Author:** Joey Flores
- **License:** MIT
- **npm:** ourpr-mcp-server
- **Source:** https://github.com/joeyaflores/ourpr-mcp-server
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 3 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-02T08:26:46.441Z
- **Version scanned:** 0.4.1
- **CVEs:** none found by OSV at scan time

## Tools

11 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `ourpr_list_runs` — Training history between two dates, newest first: date, name, type,
- `ourpr_get_run` — One activity in full: mile splits, heart rate, cadence, calories,
- `ourpr_run_stream` — A run's profile on a 10 m grid — elevation, heart rate, power,
- `ourpr_run_laps` — The laps the watch recorded for one run — the runner's own button
- `ourpr_rep_workouts` — Interval sessions found across the history, with reps and distances.
- `ourpr_detect_reps` — Whether one particular run was an interval session, and its reps.
- `ourpr_similar_terrain` — Stretches of past runs matching a distance and climb — what the
- `ourpr_training_blocks` — The goal race and its Block: race day, distance, goal time, which
- `ourpr_list_races` — Every race ourpr finds in the history, newest first, tune-ups
- `ourpr_list_plans` — The runner's planned runs between two dates: day, name, miles, time,
- `ourpr_plan_week` — Write one planned run, or a week of them, onto days still ahead. Each

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"ourpr-mcp-server\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"ourpr-mcp-server\"\n      ],\n      \"env\": {\n        \"OURPR_TOKEN\": \"<YOUR_OURPR_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `OURPR_TOKEN` — Ourpr Token (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 22, ceiling 22 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/ourpr-mcp-server
- Install plan: https://forgeregistry.com/api/v1/packages/ourpr-mcp-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/ourpr-mcp-server
- HTML page: https://forgeregistry.com/registry/ourpr-mcp-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.