OutPace
REMOTE · WWW.OUTPACE.FIT
Free step and fitness challenges on OutPace for friends, run clubs, teams and military units.
Available components
Last scanned (18 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Entertainment and Games
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 14 Nov 26 +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.
- 12 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://www.outpace.fit/api/mcp/open
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.outpace.fit | CN=YR2,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | RSA 2048 | SHA256-RSA | 572e0268d3dcf420782cbefbecc5de34075 |
| SANs: www.outpace.fit | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.outpace.fit. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fit. | DS published | 21471 | 13 | Verified |
| outpace.fit. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.outpace.fit/api/mcp/open | Verified | 200 | |
| http (plaintext) | http://www.outpace.fit/api/mcp/open | HTTPS enforced | 308 | https://www.outpace.fit/api/mcp/open |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_public_challenges Find public challenges ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
| Name | Type | Req | Description |
|---|---|---|---|
| browse_url | string | yes | – |
| challenges | array | yes | – |
| count | number | yes | – |
| note | string | yes | – |
No examples provided.
get_challenge Get a challenge ~281
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invite_code | string | – | Invite code from an invite link, needed for private challenges. |
| share_code | string | yes | The challenge share code, an outpace.fit/c/... link, or an outpace.fit/i/... invite link. |
| Name | Type | Req | Description |
|---|---|---|---|
| challenge | object | yes | – |
| closed_reason | string | – | – |
| joinable | boolean | yes | – |
No examples provided.
get_started_link Get a sign-up link that joins a challenge ~304
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| challenge | object | – | – |
| relay | object | – | – |
| requirements | string | yes | – |
| sign_in_url | string | yes | – |
| signup_url | string | yes | – |
| what_happens | string | yes | – |
No examples provided.
relay_info Weekly Relay info ~130
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| how_it_works | array | yes | – |
| next_week | – | yes | – |
| note | string | – | – |
| this_week | – | yes | – |
No examples provided.
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.
remote · www.outpace.fit
claude mcp add --transport http fit-outpace-outpace 'https://www.outpace.fit/api/mcp/open'
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.