# Beatwise Metronome (remote · metronome.zovo.one)

Keep time, find note durations

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `metronome.zovo.one`: 74/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-metronome/metronome.md), [page](https://verifymcp.io/servers/theluckystrike-metronome/metronome)

## Channel facts

- Endpoint: `https://metronome.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-23.

- **Endpoint Security**: 80/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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1019 tokens (~254/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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.
  - Supports UI / widget rendering.

## Install

### How do I install the Beatwise Metronome MCP server?

Beatwise Metronome is a hosted endpoint at https://metronome.zovo.one/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 theluckystrike-metronome 'https://metronome.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-metronome": {
      "url": "https://metronome.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-metronome": {
      "type": "http",
      "url": "https://metronome.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-metronome]
url = "https://metronome.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-metronome": {
      "type": "remote",
      "url": "https://metronome.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-metronome --url 'https://metronome.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-metronome:
    url: "https://metronome.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-metronome": {
      "Transport": "http",
      "Url": "https://metronome.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-metronome -t streamable-http -u 'https://metronome.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-metronome": {
      "type": "http",
      "url": "https://metronome.zovo.one/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-23 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 73)

First indexed and scored.

## MCP tools (3)

### `show_metronome` (~336 tokens)

Show metronome

Use this when the user wants a metronome, online metronome, 120 bpm metronome, tap tempo or a metronome for practice. Opens a live beat widget with 20 to 400 quarter-note BPM, 1 to 16 beats per bar, accents, subdivisions and an optional ramp with up to 1000 tempo stages. Reports milliseconds per beat and subdivision. The widget runs only while on screen; audio timing depends on the device. Does not record audio or detect pitch.

Input parameters:

- `accent_pattern` (array): One level per beat: 0 silent (including its subdivisions), 1 normal, 2 accented. Defaults to an accented first beat. Example: [2,1,1,1].
- `beat_unit`: Time signature denominator. Default 4. BPM remains quarter-note BPM. Example: 8 for 6/8.
- `beats_per_bar` (integer): Time signature numerator, 1 to 16. Default 4. Example: 6 for 6/8.
- `bpm` (number, required): Quarter notes per minute, 20 to 400, up to three decimal places. Example: 120.
- `ramp` (object): Optional bar-based ramp; start must match bpm. The target then holds. Example: {start_bpm:80,end_bpm:120,bars_per_step:4,bpm_per_step:5}.
- `subdivision` (string): Clicks per signature beat: none=1, eighths=2, triplets=3, sixteenths=4. Default none. Example: eighths.

Output parameters:

- `accent_pattern` (array)
- `beat_ms` (string)
- `beat_unit` (number)
- `beats_per_bar` (number)
- `bpm` (number)
- `kind` (string)
- `limits` (string)
- `quarter_ms` (string)
- `ramp`
- `subdivision` (string)
- `subdivision_ms` (string)

### `calculate_tempo_values` (~308 tokens)

Calculate tempo values

Use this when the user wants bpm to ms, a delay time calculator, tempo calculator, note cycle hertz, milliseconds to beats per minute, bar length or song length. Accepts BPM or a note duration and returns whole to sixty-fourth values, dotted and triplet, pre-delay suggestions and approximate Italian marking ranges. BPM is quarter notes per minute, 20 to 400; up to 100000 song bars. Hertz is rhythmic repetition, not pitch. Does not record audio or detect pitch.

Input parameters:

- `bars` (integer): Optional song bar count at this tempo and time signature. Example: 32.
- `beat_unit`: Time signature denominator. Default 4. BPM remains quarter-note BPM. Example: 8 for 6/8.
- `beats_per_bar` (integer): Time signature numerator, 1 to 16. Default 4. Example: 6 for 6/8.
- `bpm` (number): Quarter notes per minute, 20 to 400, up to three decimal places. Example: 120.
- `milliseconds` (number): Duration of the selected note, instead of bpm; resulting BPM must be 20 to 400. Up to three decimal places. Example: 500.
- `modifier` (string): Modifier for milliseconds: straight (default), dotted, or triplet. Example: dotted.
- `note_value` (string): Note represented by milliseconds; default quarter. Only use with milliseconds. Example: eighth.

Output parameters:

- `bar_ms` (string)
- `beat_unit` (number)
- `beats_per_bar` (number)
- `bpm` (string)
- `bpm_numeric` (number)
- `delay_note` (string)
- `kind` (string)
- `marking_note` (string)
- `markings` (array)
- `notes` (array)
- `precision` (string)
- `predelays` (array)
- `quarter_ms` (string)
- `song`

### `plan_tempo_practice` (~250 tokens)

Plan tempo practice

Use this when the user wants a metronome for practice with a tempo ladder from start to target BPM, a BPM or percent step and minutes per stage. Returns the ladder table, total time and CSV download. Supports ascending or descending 20 to 400 BPM with up to 200 stages; percent steps round to 0.001 BPM and target gets the full stage time. Does not track sessions or record audio.

Input parameters:

- `minutes_per_step` (number, required): Minutes spent at each stage, including the target, up to three decimal places. Example: 2.
- `start_bpm` (number, required): Quarter notes per minute, 20 to 400, up to three decimal places. Example: 80.
- `step` (number, required): Positive change per stage, in BPM or percent; percent is limited to 100. Up to three decimal places. Example: 5.
- `step_type` (string): Step units, default bpm. Percent uses the previous stage with a 0.001 BPM rounding. Example: percent.
- `target_bpm` (number, required): Quarter notes per minute, 20 to 400, up to three decimal places. Example: 120.

Output parameters:

- `downloads` (object)
- `kind` (string)
- `minutes_per_step` (number)
- `preview` (array)
- `rounding` (string)
- `stages` (number)
- `start_bpm` (number)
- `step` (number)
- `step_type` (string)
- `target_bpm` (number)
- `total_minutes` (string)

## Diagnostics

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

## Score history

- 2026-10-23: 74
- 2026-10-22: 73

## Common questions

### What is the Beatwise Metronome MCP server?

Beatwise Metronome is an MCP server listed in the public MCP registry as io.github.theluckystrike/metronome. Keep time, find note durations. This page covers its hosted endpoint (https://metronome.zovo.one/mcp).

### Is the Beatwise Metronome MCP server safe to use?

Beatwise Metronome scores 74 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 Beatwise Metronome MCP server expose?

Beatwise Metronome exposes 3 tools: show_metronome, calculate_tempo_values, plan_tempo_practice. Their descriptions and schemas cost roughly 894 tokens of context every time the server is loaded.

### Does the Beatwise Metronome MCP server require authentication?

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

### Is the Beatwise Metronome MCP server still maintained?

Beatwise Metronome 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.

## Links

- Remote endpoint: https://metronome.zovo.one/mcp
- Website: https://metronome.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-metronome/metronome.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-metronome/metronome.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-metronome/metronome