MCP server for your own ourpr running history: read it, and put a plan on the week ahead
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
OURPR_TOKENAPI keyrequiredYour personal access token from ourpr Settings.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
ourpr_list_runsTraining history between two dates, newest first: date, name, type,Training history between two dates, newest first: date, name, type,
No input schema was published for this tool.
ourpr_get_runOne activity in full: mile splits, heart rate, cadence, calories,One activity in full: mile splits, heart rate, cadence, calories,
No input schema was published for this tool.
ourpr_run_streamA run's profile on a 10 m grid — elevation, heart rate, power,A run's profile on a 10 m grid — elevation, heart rate, power,
No input schema was published for this tool.
ourpr_run_lapsThe laps the watch recorded for one run — the runner's own buttonThe laps the watch recorded for one run — the runner's own button
No input schema was published for this tool.
ourpr_rep_workoutsInterval sessions found across the history, with reps and distances.Interval sessions found across the history, with reps and distances.
No input schema was published for this tool.
ourpr_detect_repsWhether one particular run was an interval session, and its reps.Whether one particular run was an interval session, and its reps.
No input schema was published for this tool.
ourpr_similar_terrainStretches of past runs matching a distance and climb — what theStretches of past runs matching a distance and climb — what the
No input schema was published for this tool.
ourpr_training_blocksThe goal race and its Block: race day, distance, goal time, whichThe goal race and its Block: race day, distance, goal time, which
No input schema was published for this tool.
ourpr_list_racesEvery race ourpr finds in the history, newest first, tune-upsEvery race ourpr finds in the history, newest first, tune-ups
No input schema was published for this tool.
ourpr_list_plansThe runner's planned runs between two dates: day, name, miles, time,The runner's planned runs between two dates: day, name, miles, time,
No input schema was published for this tool.
ourpr_plan_weekWrite one planned run, or a week of them, onto days still ahead. EachWrite one planned run, or a week of them, onto days still ahead. Each
No input schema was published for this tool.
11 of 11 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for your own ourpr running history: read it, and put a plan on the week ahead
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.