# Endurance Wire (remote · endurancewire.com)

Endurance gear release dates, launch prices, generation comparisons, rumors and launch predictions.

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

## Components

- remote · `endurancewire.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-endurancewire-endurancewire/endurancewire.md), [page](https://verifymcp.io/servers/com-endurancewire-endurancewire/endurancewire)

## Channel facts

- Endpoint: `https://endurancewire.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.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-10-24.

- **Endpoint Security**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1411 tokens (~235/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Endurance Wire MCP server?

Endurance Wire is a hosted endpoint at https://endurancewire.com/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 com-endurancewire-endurancewire 'https://endurancewire.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-endurancewire-endurancewire": {
      "url": "https://endurancewire.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-endurancewire-endurancewire": {
      "type": "http",
      "url": "https://endurancewire.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-endurancewire-endurancewire]
url = "https://endurancewire.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-endurancewire-endurancewire": {
      "type": "remote",
      "url": "https://endurancewire.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-endurancewire-endurancewire --url 'https://endurancewire.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-endurancewire-endurancewire:
    url: "https://endurancewire.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-endurancewire-endurancewire": {
      "Transport": "http",
      "Url": "https://endurancewire.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-endurancewire-endurancewire -t streamable-http -u 'https://endurancewire.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-endurancewire-endurancewire": {
      "type": "http",
      "url": "https://endurancewire.com/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-10-22 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-20 (score 75, +1)

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

### 2026-10-18 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Tool coverage: 100% → 94%
- [functional regression] Schema quality: 1191 → 1411
- [functional] Server version: 1.3.0 → 1.4.0
- [functional] New tool “get_news”

### 2026-10-17 (score 74, +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-10-15 (score 73, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-13 (score 72, +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-10-12 (score 71, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-10-10 (score 66, +1)

- [functional improvement] Stability: unverified → 0.07

## MCP tools (6)

### `get_releases` (~154 tokens)

Get releases

List product releases, newest first. Filter by brand, product line, or date. Each release includes recorded case_sizes_mm, size_variants with size-attributable specifications, and buy_links. Unknown sizes are explicitly marked.

Input parameters:

- `brand` (string): One of: garmin, coros, suunto, apple, amazfit, wahoo, polar, whoop, oura
- `limit` (integer): Max results, default 50
- `line` (string): One of: running, outdoor, cycling, lifestyle, handheld, dive, aviation, golf, marine, accessories, recovery
- `since` (string): Only releases on/after this date, "YYYY" or "YYYY-MM"

Output parameters:

- `_via` (string): Source attribution for Endurance Wire
- `count` (integer)
- `releases` (array)

### `get_product` (~91 tokens)

Look up a product

Find products by (partial) name, e.g. 'fenix 9', 'forerunner 970'. Returns the release record, generation chain, case_sizes_mm, size_variants with specifications and caveats per model and case size, and buy_links. Missing size data is unknown. Do not apply generation-level battery ranges to individual sizes.

Input parameters:

- `name` (string, required): Full or partial product name

Output parameters:

- `_via` (string): Source attribution for Endurance Wire
- `count` (integer)
- `products` (array)

### `get_predictions` (~276 tokens)

Next launch windows

Predicted next-release windows per flagship family, computed from average historical release cadence. Includes overdue flags.

Input parameters:

- `family` (string): One of: fenix, fr9x, fr-entry, epix, instinct, enduro, edge10x, edgemid, venu, vivoactive, descent, imini, quatix, marq, approach, hrm, varia, rally, d2, coros-pace, coros-pace-pro, coros-apex, coros…

Output parameters:

- `_via` (string): Source attribution for Endurance Wire
- `method` (string): Forecast method and uncertainty; dates are unconfirmed
- `predictions` (array)

### `get_rumors` (~40 tokens)

Rumor tracker

Current rumors, leaks and confirmed items with confidence status and sources.

Input parameters:

- `status` (string): One of: released, confirmed, strong, speculative

Output parameters:

- `_via` (string): Source attribution for Endurance Wire
- `rumors` (array)
- `statuses` (object): Meaning of each confidence status

### `get_news` (~196 tokens)

Get news coverage

Search published news coverage, newest first. Filter by brand, tagged product, publication date or text in titles, summaries and publisher names. Returns source reports, not verified release facts. Cite the publisher and preserve uncertainty. Uses the site's published dataset, not a live web search; updated_at is the last scan time. Use next_offset with the same filters for more results.

Input parameters:

- `brand` (string)
- `limit` (integer): Max results, default 50
- `offset` (integer): Results to skip, default 0
- `product` (string): Exact release slug or partial product name, e.g. 'garmin-fenix-8-8s-8x' or 'fenix 8'. Matches tagged releases, not the whole family.
- `query` (string): Case-insensitive text search; accents are ignored
- `since` (string): Only items published on or after this date (UTC)

Output parameters:

- `_via` (string): Source attribution for Endurance Wire
- `count` (integer): Total matches before pagination
- `news` (array)
- `next_offset`: Pass as offset for the next page; null when exhausted
- `updated_at` (string): Last scan time, not the time this query ran

### `compare_generations` (~427 tokens)

Compare products and case sizes

Spec diff between two products from a comparison table. Returns case_sizes_mm and size_variants per product. Select a_size_mm and b_size_mm for size-specific specs; unresolved values are null, never substituted with generation ranges. With no size selections, specs are generation summaries. Supports two sizes of the same model. Products also include verified buy_links.

Input parameters:

- `a` (string, required): First product, e.g. 'fenix 8'
- `a_size_mm` (number): First product's case size in mm, e.g. 47. Must match a recorded case size.
- `b` (string, required): Second product, e.g. 'fenix 9'
- `b_size_mm` (number): Second product's case size in mm, e.g. 51. Must match a recorded case size.
- `family` (string, required): Table id: flagships, running-flagships, bike-computers, hr-straps, recovery-wearables, polar-street, polar-loop, tactix, fenix, forerunner, forerunner-2xx, forerunner-entry, edge, edge-mid, varia, ra…

Output parameters:

- `_via` (string): Source attribution for Endurance Wire
- `changed_count` (integer)
- `comparison_scope` (string)
- `family` (string)
- `products` (array)
- `specs` (array): Each row has values keyed by the products' comparison_label; null means unknown
- `unresolved_count` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-endurancewire-endurancewire/endurancewire#diagnostics

## Score history

- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 76
- 2026-10-21: 75
- 2026-10-20: 75
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 71
- 2026-10-10: 66
- 2026-10-08: 65

## Common questions

### What is the Endurance Wire MCP server?

Endurance Wire is an MCP server listed in the public MCP registry as com.endurancewire/endurancewire. Endurance gear release dates, launch prices, generation comparisons, rumors and launch predictions. This page covers its hosted endpoint (https://endurancewire.com/mcp).

### Is the Endurance Wire MCP server safe to use?

Endurance Wire 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 Endurance Wire MCP server expose?

Endurance Wire exposes 6 tools: get_releases, get_product, get_predictions, get_rumors, get_news, compare_generations. Their descriptions and schemas cost roughly 1,184 tokens of context every time the server is loaded.

### Does the Endurance Wire MCP server require authentication?

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

### Is the Endurance Wire MCP server still maintained?

Endurance Wire is still listed as active in the MCP registry. We last reached this channel on 24 October 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://endurancewire.com/mcp
- Website: https://endurancewire.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-endurancewire-endurancewire/endurancewire.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-endurancewire-endurancewire/endurancewire.json
- HTML version of this page: https://verifymcp.io/servers/com-endurancewire-endurancewire/endurancewire