# io.github.jmbremer/rawwatts-demo (remote · app.rawwatts.com)

No sign-in: a real cyclist's indoor rides, read-only. Ask your AI about his power and heart rate.

- Trust score: 57/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `app.rawwatts.com`: 57/100 (this document), [markdown](https://verifymcp.io/servers/jmbremer-rawwatts-demo/mcp-marco.md), [page](https://verifymcp.io/servers/jmbremer-rawwatts-demo/mcp-marco)

## Channel facts

- Endpoint: `https://app.rawwatts.com/mcp/marco`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - 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 (good).
  - Context-footprint check failed: tool/resource definitions use about 923 tokens (~131/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 io.github.jmbremer/rawwatts-demo MCP server?

io.github.jmbremer/rawwatts-demo is a hosted endpoint at https://app.rawwatts.com/mcp/marco, 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 jmbremer-rawwatts-demo 'https://app.rawwatts.com/mcp/marco'
```

### Cursor

```json
{
  "mcpServers": {
    "jmbremer-rawwatts-demo": {
      "url": "https://app.rawwatts.com/mcp/marco"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jmbremer-rawwatts-demo": {
      "type": "http",
      "url": "https://app.rawwatts.com/mcp/marco"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jmbremer-rawwatts-demo]
url = "https://app.rawwatts.com/mcp/marco"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jmbremer-rawwatts-demo": {
      "type": "remote",
      "url": "https://app.rawwatts.com/mcp/marco",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jmbremer-rawwatts-demo --url 'https://app.rawwatts.com/mcp/marco' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jmbremer-rawwatts-demo:
    url: "https://app.rawwatts.com/mcp/marco"
```

### Netclaw

```json
{
  "McpServers": {
    "jmbremer-rawwatts-demo": {
      "Transport": "http",
      "Url": "https://app.rawwatts.com/mcp/marco"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jmbremer-rawwatts-demo -t streamable-http -u 'https://app.rawwatts.com/mcp/marco'
```

### Other

```json
{
  "mcpServers": {
    "jmbremer-rawwatts-demo": {
      "type": "http",
      "url": "https://app.rawwatts.com/mcp/marco"
    }
  }
}
```

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 57, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_ride” rewrote its description, which is the text the model reads
- [security] Tool “list_rides” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 115 → 131

### 2026-11-19 (score 57, +1)

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

### 2026-11-18 (score 56, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 56)

First indexed and scored.

## MCP tools (7)

### `get_athlete` (~76 tokens)

The rider's body settings (FTP, FTP history, max HR, weight, age in years, units), the dates of their first and last ride, the ride count and when the app last synced. ftp_history only holds FTPs a test replaced ("Use as FTP"); an FTP the rider typed in is not recorded there.

### `list_rides` (~127 tokens)

The rider's rides, newest first: id, local start, duration, kJ, average and max power, average and max heart rate, kind (free, ramp, rampLite, edge, workout), the rider's effort rating (1-10, null if not rated). Dates are YYYY-MM-DD in the rider's local time, both inclusive. limit: 1-500, default 50. Ids follow the order the app synced the rides, not the ride dates.

Input parameters:

- `from_date`
- `limit` (integer)
- `to_date`

### `get_ride` (~76 tokens)

One ride's full summary as the app computed it: stats (incl. normalized power), laps, power curve, power zones, left/right balance, heart rate, DFA-alpha1 per minute (experimental), the workout ridden, the FTP used, and the rider's effort rating (1-10).

Input parameters:

- `id` (integer, required)

### `get_ride_series` (~103 tokens)

A ride's second-by-second data averaged down to resolution_s (default 30; at most 720 points, so long rides get a coarser resolution). fields from: power, target, hr, cadence, right_pct, speed, distance, step. Default: power, hr, cadence. t_s is the start of each interval in recorded seconds.

Input parameters:

- `fields`
- `id` (integer, required)
- `resolution_s` (integer)

### `get_power_curve` (~61 tokens)

Best average power per duration (5 s to 60 min) over a period, with the ride each best came from. Dates YYYY-MM-DD, inclusive; both optional (default: all rides).

Input parameters:

- `from_date`
- `to_date`

### `get_training_summary` (~64 tokens)

Per week (Monday-Sunday) for the last `weeks` weeks (default 8, max 104): rides, hours, kJ and seconds per power zone (Coggan 1-7, by each ride's FTP).

Input parameters:

- `weeks` (integer)

### `list_workouts` (~46 tokens)

Every workout set as text: the rider's own (read-only for you) and each assistant's, with who wrote it. The workout format is in save_workout's description.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jmbremer-rawwatts-demo/mcp-marco#diagnostics

## Score history

- 2026-11-21: 57
- 2026-11-20: 57
- 2026-11-19: 57
- 2026-11-18: 56
- 2026-11-17: 56

## Common questions

### What is the io.github.jmbremer/rawwatts-demo MCP server?

io.github.jmbremer/rawwatts-demo is an MCP server listed in the public MCP registry as io.github.jmbremer/rawwatts-demo. No sign-in: a real cyclist's indoor rides, read-only. Ask your AI about his power and heart rate. This page covers its hosted endpoint (https://app.rawwatts.com/mcp/marco).

### Is the io.github.jmbremer/rawwatts-demo MCP server safe to use?

io.github.jmbremer/rawwatts-demo scores 57 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 io.github.jmbremer/rawwatts-demo MCP server expose?

io.github.jmbremer/rawwatts-demo exposes 7 tools: get_athlete, list_rides, get_ride, get_ride_series, get_power_curve, and 2 more. Their descriptions and schemas cost roughly 553 tokens of context every time the server is loaded.

### Does the io.github.jmbremer/rawwatts-demo MCP server require authentication?

No. We connected to io.github.jmbremer/rawwatts-demo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.jmbremer/rawwatts-demo MCP server still maintained?

io.github.jmbremer/rawwatts-demo 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 io.github.jmbremer/rawwatts-demo MCP server?

VerifyMCP ran 11 checks on io.github.jmbremer/rawwatts-demo, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about io.github.jmbremer/rawwatts-demo: Authorization and HTTPS. 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://app.rawwatts.com/mcp/marco
- Website: https://rawwatts.com/demo/
- Changelog RSS feed: https://verifymcp.io/servers/jmbremer-rawwatts-demo/mcp-marco.xml
- Changelog JSON feed: https://verifymcp.io/servers/jmbremer-rawwatts-demo/mcp-marco/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/jmbremer-rawwatts-demo/mcp-marco.json
- HTML version of this page: https://verifymcp.io/servers/jmbremer-rawwatts-demo/mcp-marco
