ourpr. is an MCP server with 18 tools an agent can call, among them ourpr_detect_reps, ourpr_get_course, ourpr_get_course_amenities. It answers at https://ourpr.app/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 27 September 2026; the last check, on 11 November 2026, succeeded.
Measured running race courses: the climb, named hills, public water and mile markers. No account.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
ourpr_detect_reps | Whether one particular run was an interval session, and its reps. Inputs: activity_id |
ourpr_get_course | Read one published course: its place, distance, climb, how it was measured, and which streets carry it. DELIBERATELY WITHOUT the elevation profile, the amenities and the centerline. Those are three more tools, because one course payload is Inputs: slug, response_format |
ourpr_get_course_amenities | Public drinking water and toilets on the line of one course, each placed at the mile it sits at. READ THIS LIMIT BEFORE YOU ANSWER. These come from OpenStreetMap: public taps and toilets somebody mapped near the route. It is a FREQUENCY dif Inputs: slug, response_format |
ourpr_get_course_route | Where a course actually runs: its start, its finish, its bounding box, every mile marker, and the streets in the order you meet them. For a watch, hand over `page_url`: a signed-in runner sends the course to Garmin Connect from the page. Th Inputs: slug, include_polyline, response_format |
ourpr_get_course_terrain | The elevation profile of one course, sampled, plus every climb and descent ourpr. named on it. THIS IS THE TOOL FOR "what are the hills and where". Each named section carries the street it runs on, the miles it spans, its net rise or fall a Inputs: slug, points, response_format |
ourpr_get_run | 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. Inputs: activity_id |
ourpr_get_trail_system | Read one trail system: how many miles of path it holds, how many ways were mapped, where it sits, and where the measurement came from. Args: - slug (string): From ourpr_list_trail_systems. Example: 'trinity-trails'. - response_format ('mark Inputs: slug, response_format |
ourpr_list_courses | List every running course published on ourpr., with its place, distance, climb and next race date. Each course is a MEASURED centerline built from recorded runs, with elevation from a public terrain model: USGS 3DEP 10 m in the US, and the Inputs: query, kind, course_type, min_distance_mi, max_distance_mi, upcoming_only |
ourpr_list_plans | 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 alr Inputs: start_date, end_date |
ourpr_list_races | 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. Inputs: distance, limit |
ourpr_list_runs | 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, s Inputs: start_date, end_date, include_non_runs, limit |
ourpr_list_trail_systems | List every trail system ourpr. maps. A trail system is a whole network of connected paths, measured end to end, not a single route through it. Args: - response_format ('markdown' | 'json'): Default 'markdown'. Returns: { "count": number, "t Inputs: response_format |
ourpr_plan_week | 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. Inputs: plans |
ourpr_rep_workouts | Interval sessions found across the history, with reps and distances. Detection is conservative, so a session it misses is still in ourpr_list_runs. Inputs: limit |
ourpr_run_laps | The laps the watch recorded for one run — the runner's own button presses. Laps follow the workout; mile splits follow the mile. Inputs: activity_id |
ourpr_run_stream | 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, the pace change between th Inputs: activity_id |
ourpr_similar_terrain | Stretches of past runs matching a distance and climb — what the runner has already done that resembles a race they are training for. Inputs: miles, gain_ft, limit, tolerance_ft |
ourpr_training_blocks | 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 t Inputs: past |
Every block below points at https://ourpr.app/api/mcp. Pick your client and copy.
claude mcp add --transport http ourpr https://ourpr.app/api/mcp
{
"mcpServers": {
"ourpr": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://ourpr.app/api/mcp"]
}
}
}{
"mcpServers": {
"ourpr": {
"url": "https://ourpr.app/api/mcp"
}
}
}{
"servers": {
"ourpr": {
"type": "http",
"url": "https://ourpr.app/api/mcp"
}
}
}{
"context_servers": {
"ourpr": {
"url": "https://ourpr.app/api/mcp"
}
}
}{
"mcpServers": {
"ourpr": {
"serverUrl": "https://ourpr.app/api/mcp"
}
}
}{
"mcpServers": {
"ourpr": {
"url": "https://ourpr.app/api/mcp"
}
}
}name: ourpr.
version: 0.0.1
schema: v1
mcpServers:
- name: ourpr.
type: streamable-http
url: https://ourpr.app/api/mcp{
"mcpServers": {
"ourpr": {
"httpUrl": "https://ourpr.app/api/mcp"
}
}
}{
"mcpServers": {
"ourpr": {
"type": "http",
"url": "https://ourpr.app/api/mcp"
}
}
}{
"mcpServers": {
"ourpr": {
"url": "https://ourpr.app/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fourpr.app%2Fapi%2Fmcp&type=streamable_http&id=ourpr&name=ourpr.
It answered our last check on 11 November 2026 in 216 ms. Over 4 checks since 27 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
18, as returned by the server's own tools/list on 16 November 2026: ourpr_detect_reps, ourpr_get_course, ourpr_get_course_amenities, ourpr_get_course_route, ourpr_get_course_terrain, ourpr_get_run, ourpr_get_trail_system, ourpr_list_courses, and 10 more.
It answered our last check on 11 November 2026 in 216 ms. Over 4 checks since 27 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://ourpr.app/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.joeyaflores. Endpoint host: ourpr.app. ARD identifier: urn:air:io.github.joeyaflores:mcp:ourpr-courses.
First indexed 26 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.