Beatwise Metronome
REMOTE · METRONOME.ZOVO.ONE
Keep time, find note durations
Available components
Last scanned (2 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Entertainment and Games
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
- Supports UI / widget rendering.Pass
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.
- 23 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 73
First indexed and scored.
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://metronome.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 78c1af029c8a2600e14b329e7e16e29 |
| SANs: zovo.one, metronome.zovo.one, *.metronome.zovo.one | ||||||
| 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 metronome.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://metronome.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://metronome.zovo.one/mcp | HTTPS enforced | 301 | https://metronome.zovo.one/mcp |
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 →
calculate_tempo_values Calculate tempo values ~308
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| bar_ms | string | yes | – |
| beat_unit | number | yes | – |
| beats_per_bar | number | yes | – |
| bpm | string | yes | – |
| bpm_numeric | number | yes | – |
| delay_note | string | yes | – |
| kind | string | yes | – |
| marking_note | string | yes | – |
| markings | array | yes | – |
| notes | array | yes | – |
| precision | string | yes | – |
| predelays | array | yes | – |
| quarter_ms | string | yes | – |
| song | – | yes | – |
No examples provided.
plan_tempo_practice Plan tempo practice ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes_per_step | number | yes | Minutes spent at each stage, including the target, up to three decimal places. Example: 2. |
| start_bpm | number | yes | Quarter notes per minute, 20 to 400, up to three decimal places. Example: 80. |
| step | number | yes | 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 | yes | Quarter notes per minute, 20 to 400, up to three decimal places. Example: 120. |
| Name | Type | Req | Description |
|---|---|---|---|
| downloads | object | yes | – |
| kind | string | yes | – |
| minutes_per_step | number | yes | – |
| preview | array | yes | – |
| rounding | string | yes | – |
| stages | number | yes | – |
| start_bpm | number | yes | – |
| step | number | yes | – |
| step_type | string | yes | – |
| target_bpm | number | yes | – |
| total_minutes | string | yes | – |
No examples provided.
show_metronome Show metronome ~336
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| accent_pattern | array | yes | – |
| beat_ms | string | yes | – |
| beat_unit | number | yes | – |
| beats_per_bar | number | yes | – |
| bpm | number | yes | – |
| kind | string | yes | – |
| limits | string | yes | – |
| quarter_ms | string | yes | – |
| ramp | – | yes | – |
| subdivision | string | yes | – |
| subdivision_ms | string | yes | – |
No examples provided.
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.
remote · metronome.zovo.one
claude mcp add --transport http theluckystrike-metronome 'https://metronome.zovo.one/mcp'
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.