# ourpr. (remote · ourpr.app)

Measured race courses, open to all, and your own runs, Blocks and plans once you sign in.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `ourpr.app`: 72/100 (this document), [markdown](https://verifymcp.io/servers/joeyaflores-ourpr-courses/api-mcp.md), [page](https://verifymcp.io/servers/joeyaflores-ourpr-courses/api-mcp)

## Channel facts

- Endpoint: `https://ourpr.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4533 tokens (~251/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ourpr. MCP server?

ourpr. is a hosted endpoint at https://ourpr.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http joeyaflores-ourpr-courses 'https://ourpr.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "joeyaflores-ourpr-courses": {
      "url": "https://ourpr.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "joeyaflores-ourpr-courses": {
      "type": "http",
      "url": "https://ourpr.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.joeyaflores-ourpr-courses]
url = "https://ourpr.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "joeyaflores-ourpr-courses": {
      "type": "remote",
      "url": "https://ourpr.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add joeyaflores-ourpr-courses --url 'https://ourpr.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  joeyaflores-ourpr-courses:
    url: "https://ourpr.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "joeyaflores-ourpr-courses": {
      "Transport": "http",
      "Url": "https://ourpr.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add joeyaflores-ourpr-courses -t streamable-http -u 'https://ourpr.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "joeyaflores-ourpr-courses": {
      "type": "http",
      "url": "https://ourpr.app/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-27 (score 72, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “ourpr_get_course” rewrote its description, which is the text the model reads
- [security] Tool “ourpr_get_course_amenities” rewrote its description, which is the text the model reads
- [security] Tool “ourpr_get_course_terrain” rewrote its description, which is the text the model reads
- [security] Tool “ourpr_list_courses” rewrote its description, which is the text the model reads
- [security] Tool “ourpr_list_trail_systems” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 510 → 251
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “ourpr_detect_reps”
- [functional] New tool “ourpr_get_run”
- [functional] New tool “ourpr_list_plans”
- [functional] New tool “ourpr_list_races”
- [functional] New tool “ourpr_list_runs”
- [functional] New tool “ourpr_plan_week”
- [functional] New tool “ourpr_rep_workouts”
- [functional] New tool “ourpr_run_laps”
- [functional] New tool “ourpr_run_stream”
- [functional] New tool “ourpr_similar_terrain”
- [functional] New tool “ourpr_training_blocks”

### 2026-09-26 (score 71)

First indexed and scored.

## MCP tools (18)

### `ourpr_list_courses` (~786 tokens)

List published running 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 the USGS 3DEP 10 m model. It is not a course map traced by hand.

START HERE. Every other course tool takes a slug, and this is where slugs come from.

Args:
  \- query (string, optional): Match the name and the place. Partial, case-insensitive.
  \- kind ('race' | 'trail' | 'route', optional): Keep one kind.
  \- course_type ('loop' | 'out-and-back' | 'point-to-point', optional): Keep one shape.
  \- min_distance_mi / max_distance_mi (number, optional): Bound the distance in miles.
  \- upcoming_only (boolean): Keep only courses whose race date has not passed. Default false.
  \- limit (number): 1 to 50. Default 20.
  \- offset (number): Skip this many. Default 0.
  \- response_format ('markdown' | 'json'): Default 'markdown'.

Returns:
  {
    "total": number,             // matched the filters
    "count": number,             // in this answer
    "offset": number,
    "has_more": boolean,
    "next_offset": number,       // present when has_more
    "published_total": number,   // every published course
    "courses": [{
      "slug": string,            // "boston-marathon"
      "name": string,            // the event's own name, title sponsor included
      "place": string | null,    // "Hopkinton → Boston, MA"
      "kind": string,
      "course_type": string,
      "distance_mi": number,
      "climb_ft": number | null,
      "steepest_pct": number | null,
      "next_race_date": string | null,  // YYYY-MM-DD
      "days_out": number | null,        // null once the date has passed
      "page_url": string
    }]
  }

The order is the race calendar: the soonest race first, then undated courses by distance.

Examples:
  \- "What marathons does ourpr. have?" -> min_distance_mi=26
  \- "Which race is next?" -> upcoming_only=true, limit=1
  \- "Anything in Fort Worth?" -> query="fort worth"…

Input parameters:

- `course_type` (string): Keep only this shape of course.
- `kind` (string): Keep only this kind. 'race' is a published event course, 'trail' is a trail segment, 'route' is an everyday loop.
- `limit` (integer): The most courses to return.
- `max_distance_mi` (number): Keep only courses no longer than this, in miles.
- `min_distance_mi` (number): Keep only courses at least this long, in miles.
- `offset` (integer): How many courses to skip. Use it with `next_offset`.
- `query` (string): Match against the course name and its place. Case-insensitive, partial. Example: 'boston', 'fort worth', 'half'.
- `response_format` (string): Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation.
- `upcoming_only` (boolean): Keep only courses whose next race date is today or later. A course with no date is dropped by this filter.

Output parameters:

- `count` (number): Courses in this answer.
- `courses` (array)
- `has_more` (boolean)
- `next_offset` (number)
- `offset` (number)
- `published_total` (number): Every published course, before any filter.
- `total` (number): Courses that matched the filters.

### `ourpr_get_course` (~609 tokens)

Get one 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 about 83 KB and 91% of it is the profile.

Args:
  \- slug (string): From ourpr_list_courses. Example: 'boston-marathon'.
  \- response_format ('markdown' | 'json'): Default 'markdown'.

Returns:
  {
    "slug": string,
    "name": string,                  // the event's own name, title sponsor included
    "place": string | null,
    "alternate_names": string[],     // curated geographic aliases
    "kind": string, "course_type": string,
    "distance_mi": number,           // the stated race distance
    "measured_mi": number | null,    // the centerline ourpr. measured
    "next_race_date": string | null, "days_out": number | null,
    "climb_ft": number | null, "descent_ft": number | null,
    "min_ft": number | null, "max_ft": number | null, "steepest_pct": number | null,
    "provenance": string | null,     // one sentence on how it was built
    "sources": [{ "label": string, "value": string }],
    "recorded_on": string | null,    // the watch that recorded the seed run
    "main_ways": [{ "name": string, "mi": number, "share_pct": number }],
    "through": string[],             // named places the line passes through
    "photo_count": number,
    "counts": { "named_climbs_and_descents": number, "amenities": number,
                "mile_markers": number, "profile_points": number },
    "page_url": string, "gpx_url": string
  }

\`distance_mi` is what the race calls itself; `measured_mi` is what the centerline measures. They differ by a few hundredths and both are reported rather than reconciled.

Examples:
  \- "Tell me about the Boston Marathon course" -> slug="boston-marathon"
  \- "How much does San Diego climb?" -> slug="san-diego-marathon", read climb_ft
  \- Do not use when: you want the hill-by-hill shape. Use ourpr_g…

Input parameters:

- `response_format` (string): Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation.
- `slug` (string, required): The course's slug, exactly as ourpr_list_courses returns it. Example: 'boston-marathon'.

Output parameters:

- `alternate_names` (array)
- `climb_ft` (number|null)
- `counts` (object)
- `course_type` (string)
- `days_out` (number|null)
- `descent_ft` (number|null)
- `distance_mi` (number)
- `gpx_url` (string)
- `kind` (string)
- `main_ways` (array)
- `max_ft` (number|null)
- `measured_mi` (number|null)
- `min_ft` (number|null)
- `name` (string)
- `next_race_date` (string|null)
- `one_way_mi` (number|null)
- `page_url` (string)
- `photo_count` (number)
- `place` (string|null)
- `provenance` (string|null)
- `recorded_on` (string|null)
- `slug` (string)
- `sources` (array)
- `steepest_pct` (number|null)
- `through` (array)

### `ourpr_get_course_terrain` (~576 tokens)

Get a course's hills

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 and its average grade.

The elevation comes from the USGS 3DEP 10 m model sampled along the measured centerline, not from a watch barometer. A barometer drifts; the model is checked against published race figures.

Args:
  \- slug (string): From ourpr_list_courses.
  \- points (number): Elevation samples to return, 2 to 200. Default 40. The stored profile holds up to 4,873.
  \- response_format ('markdown' | 'json'): Default 'markdown'.

Returns:
  {
    "slug": string, "name": string, "distance_mi": number,
    "climb_ft": number | null, "descent_ft": number | null,
    "min_ft": number | null, "max_ft": number | null,
    "steepest_pct": number | null,
    "climb_ft_per_mi": number | null,
    "elevation_source": string,
    "profile_points_stored": number,
    "profile": [{ "mi": number, "ft": number }],
    "named_sections": [{
      "kind": "climb" | "descent", "name": string,
      "from_mi": number, "to_mi": number,
      "net_ft": number, "grade_pct": number
    }],
    "page_url": string
  }

The sampled profile always keeps the first point, the last point, the highest and the lowest, so its extremes agree with min_ft and max_ft.

A course with no named sections returns an empty array. That means the seeder found no stretch that qualified, not that the course is flat: read climb_ft.

Examples:
  \- "What are the hills on Boston?" -> slug="boston-marathon"
  \- "Is Houston flat?" -> slug="houston-marathon", read climb_ft_per_mi
  \- "Give me the profile in detail" -> points=200

Error handling:
  \- Returns the slug list suggestion when the slug is unknown.

Input parameters:

- `points` (integer): How many elevation samples to return. The stored profile holds up to 4,873 points, which no agent should read whole. 40 describes the shape; 200 is close to the source.
- `response_format` (string): Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation.
- `slug` (string, required): The course's slug.

Output parameters:

- `climb_ft` (number|null)
- `climb_ft_per_mi` (number|null)
- `descent_ft` (number|null)
- `distance_mi` (number)
- `elevation_source` (string)
- `max_ft` (number|null)
- `min_ft` (number|null)
- `name` (string)
- `named_sections` (array)
- `page_url` (string)
- `profile` (array): Sampled elevation. The highest and lowest points are kept.
- `profile_points_stored` (number)
- `slug` (string)
- `steepest_pct` (number|null)

### `ourpr_get_course_amenities` (~473 tokens)

Get water and toilets on a course

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 difference, not a category one — a race day sets up many more stops than an ordinary day has. A mapped tap can also be seasonal, shut off or gone. Never present this as an aid-station plan, and never imply the count is guaranteed.

It answers the training question instead: if I run this course on an ordinary day, where can I drink?

Args:
  \- slug (string): From ourpr_list_courses.
  \- response_format ('markdown' | 'json'): Default 'markdown'.

Returns:
  {
    "slug": string, "name": string, "distance_mi": number,
    "source": string,
    "is_race_aid_station_list": false,
    "water_count": number, "toilet_count": number,
    "longest_gap_without_water_mi": number | null,
    "longest_gap_from_mi": number | null, "longest_gap_to_mi": number | null,
    "amenities": [{ "kind": string, "mi": number, "lat": number, "lng": number }],
    "page_url": string
  }

The longest gap counts the start and the finish as ends, so a course with one water stop at mile 3 of 6 reports a 3 mile gap, not 0.

Examples:
  \- "Where can I refill on the Cowtown ultra?" -> slug="cowtown-ultra-marathon"
  \- "How far do I go without water on Boston?" -> read longest_gap_without_water_mi
  \- Do not use when: you want race-day aid stations. ourpr. does not hold those.

Error handling:
  \- A course with no mapped amenity returns empty arrays and zero counts. That means none is mapped, not that none exists.

Input parameters:

- `response_format` (string): Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation.
- `slug` (string, required): The course's slug.

Output parameters:

- `amenities` (array)
- `distance_mi` (number)
- `is_race_aid_station_list` (boolean): Always false. These are public amenities, not race aid stations.
- `longest_gap_from_mi` (number|null)
- `longest_gap_to_mi` (number|null)
- `longest_gap_without_water_mi` (number|null)
- `name` (string)
- `page_url` (string)
- `slug` (string)
- `source` (string)
- `toilet_count` (number)
- `water_count` (number)

### `ourpr_get_course_route` (~462 tokens)

Get a course's line

Where a course actually runs: its start, its finish, its bounding box, every mile marker, and the streets in the order you meet them.

The GPX file is free and needs no account. Hand `gpx_url` to a person who wants the course on a watch.

Args:
  \- slug (string): From ourpr_list_courses.
  \- include_polyline (boolean): Add the encoded centerline, about 9,800 characters. Default false.
  \- response_format ('markdown' | 'json'): Default 'markdown'.

Returns:
  {
    "slug": string, "name": string, "course_type": string, "distance_mi": number,
    "start": { "lat": number, "lng": number } | null,
    "finish": { "lat": number, "lng": number } | null,
    "bbox": { "min_lat": number, "min_lng": number, "max_lat": number, "max_lng": number } | null,
    "mile_markers": [{ "mile": number, "lat": number, "lng": number }],
    "streets_in_order": [{ "name": string, "from_mi": number, "to_mi": number }],
    "polyline": string | null,
    "gpx_url": string, "page_url": string
  }

On an out-and-back the start and the finish are the same point, by design.

Examples:
  \- "Send me the Boston course for my watch" -> read gpx_url
  \- "What streets does Dallas run down?" -> read streets_in_order
  \- "Where does Honolulu start?" -> read start

Error handling:
  \- Returns the slug list suggestion when the slug is unknown.

Input parameters:

- `include_polyline` (boolean): Add the encoded centerline. It runs to about 9,800 characters and only helps if you will decode it. Leave it off and hand over `gpx_url` instead.
- `response_format` (string): Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation.
- `slug` (string, required): The course's slug.

Output parameters:

- `bbox`
- `course_type` (string)
- `distance_mi` (number)
- `finish`
- `gpx_url` (string)
- `mile_markers` (array)
- `name` (string)
- `page_url` (string)
- `polyline` (string|null)
- `slug` (string)
- `start`
- `streets_in_order` (array)

### `ourpr_list_trail_systems` (~237 tokens)

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,
    "trail_systems": [{
      "slug": string,          // "trinity-trails"
      "name": string,
      "region": string | null, // "Fort Worth, TX"
      "total_mi": number,      // the whole network, all branches
      "page_url": string
    }]
  }

Examples:
  \- "What trail networks does ourpr. map?" -> no arguments
  \- "How big is Trinity Trails?" -> read total_mi, or call ourpr_get_trail_system
  \- Do not use when: you want one measured route. Use ourpr_list_courses with kind='trail'.

Input parameters:

- `response_format` (string): Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation.

Output parameters:

- `count` (number)
- `trail_systems` (array)

### `ourpr_get_trail_system` (~323 tokens)

Get one 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 ('markdown' | 'json'): Default 'markdown'.

Returns:
  {
    "slug": string, "name": string, "region": string | null,
    "total_mi": number,           // every branch summed
    "mapped_ways": number | null, // OpenStreetMap ways in the network
    "source": string | null,      // how the network and its coverage were built
    "bbox": { "min_lat": number, "min_lng": number,
              "max_lat": number, "max_lng": number } | null,
    "page_url": string
  }

\`total_mi` counts the whole network. It is not a distance anyone runs in one go.

Examples:
  \- "How many miles of trail are in Fort Worth?" -> slug="trinity-trails"
  \- "Where does the network reach?" -> read bbox

Error handling:
  \- Returns the slug list suggestion when the slug is unknown.

Input parameters:

- `response_format` (string): Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation.
- `slug` (string, required): The trail system's slug. Example: 'trinity-trails'.

Output parameters:

- `bbox`
- `mapped_ways` (number|null)
- `name` (string)
- `page_url` (string)
- `region` (string|null)
- `slug` (string)
- `source` (string|null)
- `total_mi` (number)

### `ourpr_list_runs` (~161 tokens)

List runs in a date range

Training history between two dates, newest first: date, name, type, miles, pace, time, elevation, average heart rate. Start here for totals, streaks, trends, or finding a run. For one run's splits, use ourpr_get_run with an id from here.

Input parameters:

- `end_date` (string, required): 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, required): First day to include, YYYY-MM-DD. Example: 2026-01-01

Output parameters:

- `returned` (number)
- `runs` (array)
- `total_in_window` (number)
- `truncated` (boolean)

### `ourpr_get_run` (~63 tokens)

Get one run in full

One activity in full: mile splits, heart rate, cadence, calories, device. Id comes from ourpr_list_runs. For the profile along the route, use ourpr_run_stream.

Input parameters:

- `activity_id` (string, required): Run id from ourpr_list_runs.

Output parameters:

- `run` (object)
- `splits` (array)

### `ourpr_run_stream` (~71 tokens)

Get a run's elevation and sensor profile

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. No profile is a normal answer for an indoor run.

Input parameters:

- `activity_id` (string, required): Run id from ourpr_list_runs.

Output parameters:

- `channels` (object)
- `grid_m` (number)
- `samples` (number)
- `total_miles` (number)

### `ourpr_run_laps` (~54 tokens)

Get a run's laps

The laps the watch recorded for one run — the runner's own button presses. Laps follow the workout; mile splits follow the mile.

Input parameters:

- `activity_id` (string, required): Run id from ourpr_list_runs.

Output parameters:

- `laps` (array)

### `ourpr_rep_workouts` (~53 tokens)

Find rep workouts across the history

Interval sessions found across the history, with reps and distances. Detection is conservative, so a session it misses is still in ourpr_list_runs.

Input parameters:

- `limit` (integer): How many recent activities to read.

Output parameters:

- `scanned` (number)
- `workouts` (array)

### `ourpr_detect_reps` (~39 tokens)

Look for reps in one run

Whether one particular run was an interval session, and its reps.

Input parameters:

- `activity_id` (string, required): Run id from ourpr_list_runs.

Output parameters:

- `detection` (object)

### `ourpr_similar_terrain` (~86 tokens)

Find runs over comparable ground

Stretches of past runs matching a distance and climb — what the runner has already done that resembles a race they are training for.

Input parameters:

- `gain_ft` (number, required): Target climb in feet.
- `limit` (integer): How many to return.
- `miles` (number, required): Target distance in miles.
- `tolerance_ft` (number): Climb tolerance, feet.

Output parameters:

- `matches` (array)
- `scanned` (number)

### `ourpr_training_blocks` (~89 tokens)

Get the goal race and 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 to Sunday weeks before a race.

Input parameters:

- `past` (integer): How many past Blocks to include, newest first.

Output parameters:

- `goal`
- `past` (array)
- `total_races` (number)

### `ourpr_list_races` (~84 tokens)

List the races in the history

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.

Input parameters:

- `distance` (string): Only races at this distance.
- `limit` (integer): Most rows to return.

Output parameters:

- `fastest` (array)
- `races` (array)
- `returned` (number)
- `total` (number)

### `ourpr_list_plans` (~123 tokens)

List planned runs in a date range

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.

Input parameters:

- `end_date` (string): Last day, YYYY-MM-DD. Default 13 days after the first.
- `start_date` (string): First day, YYYY-MM-DD. Default yesterday, so today is in the window in every time zone.

Output parameters:

- `end_date` (string)
- `plans` (array)
- `start_date` (string)
- `truncated` (boolean)

### `ourpr_plan_week` (~77 tokens)

Put runs on the runner's 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.

Input parameters:

- `plans` (array, required): One run, or up to fourteen.

Output parameters:

- `written` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/joeyaflores-ourpr-courses/api-mcp#diagnostics

## Score history

- 2026-09-27: 72
- 2026-09-26: 71

## Common questions

### What is the ourpr. MCP server?

ourpr. is an MCP server listed in the public MCP registry as io.github.joeyaflores/ourpr-courses. Measured race courses, open to all, and your own runs, Blocks and plans once you sign in. This page covers its hosted endpoint (https://ourpr.app/api/mcp).

### Is the ourpr. MCP server safe to use?

ourpr. scores 72 out of 100 on VerifyMCP. 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 ourpr. MCP server expose?

ourpr. exposes 18 tools: ourpr_list_courses, ourpr_get_course, ourpr_get_course_terrain, ourpr_get_course_amenities, ourpr_get_course_route, and 13 more. Their descriptions and schemas cost roughly 4,366 tokens of context every time the server is loaded.

### Does the ourpr. MCP server require authentication?

No. We connected to ourpr. without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ourpr. MCP server still maintained?

ourpr. is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://ourpr.app/api/mcp
- Website: https://ourpr.app/courses/mcp
- Changelog RSS feed: https://verifymcp.io/servers/joeyaflores-ourpr-courses/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/joeyaflores-ourpr-courses/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/joeyaflores-ourpr-courses/api-mcp