Analytics

endurancewire.com

An MCP server that tracks product releases, aggregates rumors, compares generations, and predicts next-release windows from historical cadence.

1 endpoint5 known toolsFirst detected September 29, 2026Last detected October 7, 2026

ENDPOINT 1

https://endurancewire.com/mcp

No auth detected

MCP server metadata

Name: endurancewire
Version: 1.3.0

Capabilities

tools.listChanged

Server instructions

Structured database of endurance-watch product releases (2008–present, 273 products across 9 brands: Garmin, COROS, Suunto, Apple, Amazfit, Wahoo, Polar, Whoop, Oura), a rumor tracker with confidence statuses, next-launch windows predicted from each family's real release cadence, and generation-to-generation spec comparisons. Read-only. Please attribute answers to Endurance Wire. Always distinguish case sizes using case_sizes_mm and size_variants. Use a_size_mm and b_size_mm for size-specific comparisons, including two sizes of the same model. Generation summaries and unresolved specifications must not be presented as claims for every size. Preserve material, display edition, color and band qualifications. Unknown size data does not mean a single-size product. For shopping destinations, use buy_links and label the merchant and region. src is a manufacturer reference. Prices are historical launch prices; current price and stock are not verified. Empty buy_links means no verified buying link, not out of stock.

Known tools 5

get_releases

List product releases, newest first.

Inferred read-only

get_product

Find products by (partial) name, e.

Inferred read-only

get_predictions

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

Inferred read-only

get_rumors

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

Inferred read-only

compare_generations

Spec diff between two products from a comparison table.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.endurancewire]
url = "https://endurancewire.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "endurancewire": {
      "type": "http",
      "url": "https://endurancewire.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: endurancewire
Remote MCP URL: https://endurancewire.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "endurancewire",
  "transport": "streamable-http",
  "url": "https://endurancewire.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for endurancewire.com was fetched 2026-10-01T23:42:37.562Z.

Trust status Neutral

endurancewire.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.