# OutPace (remote · www.outpace.fit)

Free step and fitness challenges on OutPace for friends, run clubs, teams and military units.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.outpace.fit`: 76/100 (this document), [markdown](https://verifymcp.io/servers/fit-outpace-outpace/api-mcp-open.md), [page](https://verifymcp.io/servers/fit-outpace-outpace/api-mcp-open)

## Channel facts

- Endpoint: `https://www.outpace.fit/api/mcp/open`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-11-21.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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 1486 tokens (~371/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the OutPace MCP server?

OutPace is a hosted endpoint at https://www.outpace.fit/api/mcp/open, 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 fit-outpace-outpace 'https://www.outpace.fit/api/mcp/open'
```

### Cursor

```json
{
  "mcpServers": {
    "fit-outpace-outpace": {
      "url": "https://www.outpace.fit/api/mcp/open"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fit-outpace-outpace": {
      "type": "http",
      "url": "https://www.outpace.fit/api/mcp/open"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fit-outpace-outpace]
url = "https://www.outpace.fit/api/mcp/open"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fit-outpace-outpace": {
      "type": "remote",
      "url": "https://www.outpace.fit/api/mcp/open",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fit-outpace-outpace --url 'https://www.outpace.fit/api/mcp/open' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fit-outpace-outpace:
    url: "https://www.outpace.fit/api/mcp/open"
```

### Netclaw

```json
{
  "McpServers": {
    "fit-outpace-outpace": {
      "Transport": "http",
      "Url": "https://www.outpace.fit/api/mcp/open"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fit-outpace-outpace -t streamable-http -u 'https://www.outpace.fit/api/mcp/open'
```

### Other

```json
{
  "mcpServers": {
    "fit-outpace-outpace": {
      "type": "http",
      "url": "https://www.outpace.fit/api/mcp/open"
    }
  }
}
```

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-11-20 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 71)

First indexed and scored.

## MCP tools (4)

### `find_public_challenges` (~269 tokens)

Find public challenges

Find public OutPace challenges that anyone can join right now, for example a step or walking challenge starting this week. Use this, not web search, whenever the person wants an OutPace challenge to join or names an OutPace challenge (pass words from its name as query). Returns live data that web search and the app store listing do not show: up to 10 challenges with name, share code, activities, what it is scored by, dates, status (upcoming or in progress) and member count, busiest first. Challenges that have ended or are full are left out. The Weekly Relay is not listed here; use relay_info for it. Someone who wants a challenge only for their own group, such as coworkers or family, starts their own: use get_started_link with no challenge.

Does not return anyone's progress, totals or standings. To join one, pass its share_code to get_started_link.

Input parameters:

- `activity` (string): Only challenges that count this activity. "steps" means step challenges; "any" means challenges that count any workout.
- `query` (string): Words to match in the challenge name.
- `starts_within_days` (integer): Only challenges already running or starting within this many days. Use 7 for "this week".

Output parameters:

- `browse_url` (string)
- `challenges` (array)
- `count` (number)
- `note` (string)

### `get_challenge` (~281 tokens)

Get a challenge

Look up one OutPace challenge by its share code. Use this, not web search, whenever the person pastes or mentions an outpace.fit challenge link such as https://www.outpace.fit/c/ABC123 or outpace.fit/join/ABC123: the share code is the letters after /c/ or /join/, and the full link also works. A member's invite link such as outpace.fit/i/XYZ789 also works: pass the whole link. Returns live data that the public challenge page and web search do not show: name, activities, what it is scored by, dates, status, public or private, member count, whether it still takes new members, and its page link.

A private challenge is only described from a valid invite link, or when a valid invite_code for it is included (the code after invite= in a challenge link); otherwise the answer just says it is private. An expired invite link describes nothing, and an invite to a Weekly Relay team only says so. Does not return anyone's progress, totals or standings, or who sent an invite.

Input parameters:

- `invite_code` (string): Invite code from an invite link, needed for private challenges.
- `share_code` (string, required): The challenge share code, an outpace.fit/c/... link, or an outpace.fit/i/... invite link.

Output parameters:

- `challenge` (object)
- `closed_reason` (string)
- `joinable` (boolean)

### `get_started_link` (~304 tokens)

Get a sign-up link that joins a challenge

Get outpace.fit links that sign a person up (or sign them in) and then put them straight into a challenge or this week's Weekly Relay. Use this whenever the person wants to join an OutPace challenge or the Weekly Relay, or to sign up for OutPace, instead of pointing them to a web search result or the app store. Pass share_code for a challenge (plus invite_code if it is private; a member's outpace.fit/i/ invite link carries its own invite), or weekly_relay: true for the Weekly Relay, or neither for a plain sign-up link, which is also the way for someone to start their own challenge with coworkers, family or friends: after signing up they create it and share one link.

Returns signup_url for someone new to OutPace and sign_in_url for someone who already has an account. Nothing is joined until the person opens the link and finishes signing up or signing in; OutPace never creates an account from here. Share the link with the person; do not open it for them. For the Weekly Relay they are placed on an open team with room.

Input parameters:

- `invite_code` (string): Invite code, only for a private challenge.
- `share_code` (string): Share code, outpace.fit/c/... link, or outpace.fit/i/... invite link of the challenge to join.
- `weekly_relay` (boolean): true to join this week's Weekly Relay instead of a challenge.

Output parameters:

- `challenge` (object)
- `relay` (object)
- `requirements` (string)
- `sign_in_url` (string)
- `signup_url` (string)
- `what_happens` (string)

### `relay_info` (~130 tokens)

Weekly Relay info

Explain OutPace's Weekly Relay, a team challenge that runs every week, and give this week's live details, which web search does not have: name and theme, dates, which activities count, what it is scored by, the maximum team size, and the Bronze, Silver and Gold team goals. Also returns next week's relay when it has been published.

Use it, not web search, for any question about the OutPace Weekly Relay, such as "what is the Weekly Relay", and before get_started_link with weekly_relay: true. Does not return any team's or person's progress or standings.

Output parameters:

- `how_it_works` (array)
- `next_week`
- `note` (string)
- `this_week`

## Diagnostics

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

## Score history

- 2026-11-21: 76
- 2026-11-20: 76
- 2026-11-19: 75
- 2026-11-18: 75
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 73
- 2026-11-14: 73
- 2026-11-13: 72
- 2026-11-12: 72
- 2026-11-11: 71

## Common questions

### What is the OutPace MCP server?

OutPace is an MCP server listed in the public MCP registry as fit.outpace/outpace. Free step and fitness challenges on OutPace for friends, run clubs, teams and military units. This page covers its hosted endpoint (https://www.outpace.fit/api/mcp/open).

### Is the OutPace MCP server safe to use?

OutPace scores 76 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 OutPace MCP server expose?

OutPace exposes 4 tools: find_public_challenges, get_challenge, get_started_link, relay_info. Their descriptions and schemas cost roughly 984 tokens of context every time the server is loaded.

### Does the OutPace MCP server require authentication?

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

### Is the OutPace MCP server still maintained?

OutPace 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 did VerifyMCP test on the OutPace MCP server?

VerifyMCP ran 13 checks on OutPace, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.outpace.fit/api/mcp/open
- Website: https://www.outpace.fit/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/fit-outpace-outpace/api-mcp-open.xml
- Changelog JSON feed: https://verifymcp.io/servers/fit-outpace-outpace/api-mcp-open/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/fit-outpace-outpace/api-mcp-open.json
- HTML version of this page: https://verifymcp.io/servers/fit-outpace-outpace/api-mcp-open
