Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Endurance Wire

REMOTE · ENDURANCEWIRE.COM

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

+3 this week 76 Trust /100

Last scanned (22 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 23 Oct 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
  • 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 22 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 20 Oct 26 +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.

  • 18 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 100% → 94% ▼ functional
    • Schema quality: 1191 → 1411 ▼ functional
    • Server version: 1.3.0 → 1.4.0 functional
    • New tool “get_news” functional
  • 17 Oct 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.

  • 15 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 13 Oct 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.

  • 12 Oct 26 +5
    • HTTPS: unverified → pass ▲ security
  • 10 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
Diagnostics

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 23 Oct 2026 · Probed https://endurancewire.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=endurancewire.com CN=WE1,O=Google Trust Services,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA256 a92bb3285e21d4ba13a100275df251c3
SANs: endurancewire.com, www.endurancewire.com, *.www.endurancewire.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of endurancewire.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
endurancewire.com. absent 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://endurancewire.com/mcp Verified 200
http (plaintext) http://endurancewire.com/mcp HTTPS enforced 301 https://endurancewire.com/mcp
MCP tools · 6 exposed · ~1,184 tokens

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 →

Tool Tokens
compare_generations ~427

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.

NameTypeReqDescription
astringyesFirst product, e.g. 'fenix 8'
a_size_mmnumber–First product's case size in mm, e.g. 47. Must match a recorded case size.
bstringyesSecond product, e.g. 'fenix 9'
b_size_mmnumber–Second product's case size in mm, e.g. 51. Must match a recorded case size.
familystringyesTable 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…
NameTypeReqDescription
_viastringyesSource attribution for Endurance Wire
changed_countintegeryes–
comparison_scopestringyes–
familystringyes–
productsarrayyes–
specsarrayyesEach row has values keyed by the products' comparison_label; null means unknown
unresolved_countintegeryes–

No examples provided.

get_news ~196

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.

NameTypeReqDescription
brandstring––
limitinteger–Max results, default 50
offsetinteger–Results to skip, default 0
productstring–Exact release slug or partial product name, e.g. 'garmin-fenix-8-8s-8x' or 'fenix 8'. Matches tagged releases, not the whole family.
querystring–Case-insensitive text search; accents are ignored
sincestring–Only items published on or after this date (UTC)
NameTypeReqDescription
_viastringyesSource attribution for Endurance Wire
countintegeryesTotal matches before pagination
newsarrayyes–
next_offset–yesPass as offset for the next page; null when exhausted
updated_atstringyesLast scan time, not the time this query ran

No examples provided.

get_predictions ~276

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

NameTypeReqDescription
familystring–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…
NameTypeReqDescription
_viastringyesSource attribution for Endurance Wire
methodstringyesForecast method and uncertainty; dates are unconfirmed
predictionsarrayyes–

No examples provided.

get_product ~91

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.

NameTypeReqDescription
namestringyesFull or partial product name
NameTypeReqDescription
_viastringyesSource attribution for Endurance Wire
countintegeryes–
productsarrayyes–

No examples provided.

get_releases ~154

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.

NameTypeReqDescription
brandstring–One of: garmin, coros, suunto, apple, amazfit, wahoo, polar, whoop, oura
limitinteger–Max results, default 50
linestring–One of: running, outdoor, cycling, lifestyle, handheld, dive, aviation, golf, marine, accessories, recovery
sincestring–Only releases on/after this date, "YYYY" or "YYYY-MM"
NameTypeReqDescription
_viastringyesSource attribution for Endurance Wire
countintegeryes–
releasesarrayyes–

No examples provided.

get_rumors ~40

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

NameTypeReqDescription
statusstring–One of: released, confirmed, strong, speculative
NameTypeReqDescription
_viastringyesSource attribution for Endurance Wire
rumorsarrayyes–
statusesobjectyesMeaning of each confidence status

No examples provided.

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.

remote · endurancewire.com

# add to Claude Code
claude mcp add --transport http com-endurancewire-endurancewire 'https://endurancewire.com/mcp'
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 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.