# Cesure (remote · api.cesure.app)

Write, edit, transpose and play guitar tabs and staff notation in Cesure.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `api.cesure.app`: 66/100 (this document), [markdown](https://verifymcp.io/servers/app-cesure-cesure/api.md), [page](https://verifymcp.io/servers/app-cesure-cesure/api)

## Channel facts

- Endpoint: `https://api.cesure.app/mcp`
- 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-10-24.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (edit_measures).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 36/100
  - 0% 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 3669 tokens (~244/item across 15 items; 14 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 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 Cesure MCP server?

Cesure is a hosted endpoint at https://api.cesure.app/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 app-cesure-cesure 'https://api.cesure.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-cesure-cesure": {
      "url": "https://api.cesure.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-cesure-cesure": {
      "type": "http",
      "url": "https://api.cesure.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-cesure-cesure]
url = "https://api.cesure.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-cesure-cesure": {
      "type": "remote",
      "url": "https://api.cesure.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-cesure-cesure --url 'https://api.cesure.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-cesure-cesure:
    url: "https://api.cesure.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-cesure-cesure": {
      "Transport": "http",
      "Url": "https://api.cesure.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-cesure-cesure -t streamable-http -u 'https://api.cesure.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-cesure-cesure": {
      "type": "http",
      "url": "https://api.cesure.app/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-22 (score 66, +1)

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

### 2026-10-20 (score 65, +1)

- [security] Resource “cesure_player” now points somewhere else: ui://cesure/player-0.7.0+bb4e383 → ui://cesure/player-0.8.1+530f487
- [security] Tool “edit_measures” rewrote its description, which is the text the model reads
- [security] Tool “import_score” rewrote its description, which is the text the model reads
- [security] Tool “search_catalog” rewrote its description, which is the text the model reads

### 2026-10-19 (score 64, 0)

- [security] Resource “cesure_player” now points somewhere else: ui://cesure/player-0.7.0+d2663ee → ui://cesure/player-0.7.0+bb4e383

### 2026-10-18 (score 64, +1)

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

### 2026-10-16 (score 63, +1)

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

### 2026-10-14 (score 62, +1)

- [security] Resource “cesure_player” now points somewhere else: ui://cesure/player-0.7.0+ddf0361 → ui://cesure/player-0.7.0+d2663ee
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “create_score” rewrote its description, which is the text the model reads
- [security] Tool “edit_measures” rewrote its description, which is the text the model reads
- [security] Tool “list_my_scores” rewrote its description, which is the text the model reads
- [security] Tool “open_in_cesure” rewrote its description, which is the text the model reads
- [security] Tool “organize_my_scores” rewrote its description, which is the text the model reads
- [security] Tool “transpose” rewrote its description, which is the text the model reads
- [cosmetic] “transpose” added an optional parameter “harmonicsOffTheNeck”
- [cosmetic] “transpose” added an optional parameter “notesOffTheNeck”

### 2026-10-13 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 61)

First indexed and scored.

## MCP tools (14)

### `create_score` (~823 tokens)

Create a score

Create a score you write as a .cesure and open it as a draft, e.g. {"version":2,"score":{"title":"Song","tempo":96,"tracks":[{"name":"Guitar","instrument":"GUITAR","measures":[{"staves":[{"voices":["(0.6 2.5 2.4).2 r.2"]}]}]},{"name":"Bass","instrument":"BASS","tuning":[{"note":"G","octave":2},{"note":"D","octave":2},{"note":"A","octave":1},{"note":"E","octave":1}],"measures":[{"staves":[{"voices":["0.4.2 r.2"]}]}]}]}} (a track without tuning is a guitar in standard tuning; tuning lists the open strings from string 1). Every measure must read and fill its time signature, or nothing is created and the refusal names each fault with its place. Measure notation (.cesure): each voice is one string of beats separated by spaces. beat = content.duration[{d | tu 3}]; content = fret.string[{note props}] | pitch | (note note …) | r. Durations, on EVERY beat: 1 whole, 2 half, 4 quarter, 8, 16, 32, 64. Strings from 1 (the highest); x as fret mutes. A pitch (C4 = middle C, F#3, Bb2) lets Cesure choose string and fret; a staff is all by pitch or all fret.string. Beat props: d dotted, tu 3 triplet on each beat of the group. Note props: t tie, h hammer/pull-off and sl slide to the next note on that string, v vibrato, b (0 4) a whole-tone bend. EACH VOICE FILLS ITS TIME SIGNATURE EXACTLY: 4/4 = 4 quarters = 8 eighths, 3/4 = 3 quarters, 6/8 = 6 eighths; rests complete a short one. A measure without numerator/denominator is 4/4, whatever came before. A second voice (a bass under a melody) is a second string in voices. Examples (4/4): "5.3.4 7.3.4 r.2" (fret 5 then 7 on string 3 (strings from 1, the highest), quarters; a half rest); "(0.1 1.2 0.3).2 x.6.4 r.4" (a chord, a half; a muted note); "E4.8 F#4.8 G4.4 Bb3.2" (notes by pitch (C4 = middle C): Cesure chooses string and fret); "5.3.4{d} 5.3.8 2.1.8{tu 3} 3.1.8{tu 3} 5.1.8{tu 3} 7.2{h}.8 8.2.8" (dotted quarter; a triplet of eighths (each beat carries it); a hammer-on to the next note); "5.3.2 5.3{t}.4 7.2{sl}.8 9.2{v}.8" (a tie to t…

Input parameters:

- `score` (string, required): The score, a .cesure written in the notation described above.

### `import_score` (~98 tokens)

Import a score

Open as a draft a score the person gives whole: a .cesure file's text, AlphaTex, or an "Open in Cesure" link. The score is taken as it is, never rewritten. A link to any other page (a video, a recording) opens nothing: Cesure reads no page.

Input parameters:

- `score` (string, required): The .cesure text, AlphaTex, or Open in Cesure link, verbatim.

### `read_score` (~169 tokens)

Read measures

Read measures from..to of a track of the draft (all by default, 200 at most a call: past them, the answer's more says where to go on) as .cesure measures — id, time signature, voices in the compact notation (second voice, hands, ties included) — with the repeat signs and tempo changes of those measures, by id, a summary of the score and one of the track.

Input parameters:

- `draft` (string, required): The draft: the id a previous tool gave (draft).
- `from` (integer): First measure, from 1 (default 1).
- `to` (integer): Last measure (default the last; at most 200 are read a call).
- `track` (integer): The track, from 1 (default 1).

### `edit_measures` (~950 tokens)

Edit measures

Rewrite measures from..to (numbers, inclusive) of ONE track of the draft with .cesure measures, as read_score returns them; to = from - 1 inserts before from. A measure written with its id stays that measure, even rewritten; one written without its id is a new measure, and the one it stood for is removed with what it carried (a repeat it opened, say). A measure of the range left out is removed, and measures [] removes the whole range. The other tracks follow column by column, as in the editor: a column is inserted, removed or given a time signature on every track; its repeat signs are carried as the editor carries them, and a tempo change stays on its column (on the next one when its column is removed), so no other column changes tempo. A note may be written by its pitch (E4, Bb3) in place of fret.string: Cesure chooses its string and fret, and never moves a note written with its string. The answer names the measures written. A written measure that does not read or does not fill its time signature refuses the whole call, the refusal naming each fault with its place; a measure sent back unchanged (same id and content) is kept as it was. Measure notation (.cesure): each voice is one string of beats separated by spaces. beat = content.duration[{d | tu 3}]; content = fret.string[{note props}] | pitch | (note note …) | r. Durations, on EVERY beat: 1 whole, 2 half, 4 quarter, 8, 16, 32, 64. Strings from 1 (the highest); x as fret mutes. A pitch (C4 = middle C, F#3, Bb2) lets Cesure choose string and fret; a staff is all by pitch or all fret.string. Beat props: d dotted, tu 3 triplet on each beat of the group. Note props: t tie, h hammer/pull-off and sl slide to the next note on that string, v vibrato, b (0 4) a whole-tone bend. EACH VOICE FILLS ITS TIME SIGNATURE EXACTLY: 4/4 = 4 quarters = 8 eighths, 3/4 = 3 quarters, 6/8 = 6 eighths; rests complete a short one. A measure without numerator/denominator is 4/4, whatever came before. A second voice (a bass under a melody)…

Input parameters:

- `draft` (string, required): The draft: the id a previous tool gave (draft).
- `from` (integer, required): First measure replaced, from 1.
- `measures` (array, required): The new measures, .cesure measure objects as read_score returns them; [] removes the range.
- `to` (integer, required): Last measure replaced; from - 1 to insert.
- `track` (integer): The track, from 1 (default 1).

### `transpose` (~372 tokens)

Transpose

Shift the notes of the draft by some semitones; the placement follows, and no note keeps a wrong pitch. A note no string of its track carries at its shifted pitch goes where notesOffTheNeck says: retune_lowest_string tunes the lowest string of the track down to the lowest of those it carries (4 semitones at most), then moves the others by octaves; change_octave moves each by the octaves that put it on the neck. A harmonic that rings in its own form at no shifted string goes where harmonicsOffTheNeck says: keep_harmonic keeps it a harmonic at the octave that holds it, play_fretted plays it as a fretted note at its pitch, losing the harmonic's timbre. By default the lowest string when it carries the notes with no octave, else octaves, and harmonics kept when an octave holds them; play_fretted when no harmonic leaves the neck changes nothing. A choice that cannot place the notes is refused, saying why and naming the one that can. The answer names each string tuned down (retunedStrings: track, string, from, to) and counts the notes moved by octaves (notesMovedByOctaves) and the harmonics played fretted (harmonicsPlayedFretted).

Input parameters:

- `draft` (string, required): The draft: the id a previous tool gave (draft).
- `harmonicsOffTheNeck` (string): keep_harmonic or play_fretted (default the first when an octave holds the harmonic).
- `notesOffTheNeck` (string): retune_lowest_string or change_octave (default the first when it carries the notes with no octave).
- `semitones` (integer, required): Semitones, -24 to 24.

### `refinger` (~120 tokens)

Place the notes again

Place the notes of the draft again on the neck (string and fret), keeping their pitches: mode auto, standard (lowest frets) or optimized (fewest hand moves); searchCapo lets it choose a capo.

Input parameters:

- `draft` (string, required): The draft: the id a previous tool gave (draft).
- `mode` (string): auto (default), standard or optimized.
- `searchCapo` (boolean): Let the placement choose a capo (default false).
- `track` (integer): The track, from 1 (default every track).

### `undo_last_change` (~94 tokens)

Undo the last change

Give the draft back the score it held before its last change (edit_measures, transpose, refinger, or an undo): the score it holds now becomes the one before, so calling it again redoes. One step only, and only when Cesure had room to keep that score; it says so when it had not.

Input parameters:

- `draft` (string, required): The draft: the id a previous tool gave (draft).

### `search_catalog` (~93 tokens)

Search the catalog

Search Cesure's catalog of free pieces by words of a title, a composer or both: a piece is found when each word is in one of them, a short joining word such as 'by' aside; returns title, artist, licence and link.

Input parameters:

- `language` (string): en (default), fr or es.
- `query` (string): Words of a title or a composer; empty lists the catalog.

### `open_in_cesure` (~84 tokens)

Open in Cesure

Show the draft in the Cesure player, to read and hear it. Where the host draws apps, the player plays the draft in the conversation; everywhere, the answer gives the short link that opens it in Cesure, with no account, and the score's summary.

Input parameters:

- `draft` (string, required): The draft: the id a previous tool gave (draft).

### `list_my_scores` (~113 tokens)

List my scores

The scores of the person's linked Cesure account ("My scores"), the most recently changed at the top, 200 a call (offset skips that many; when there are more, the answer's more gives the next offset): id, title, when last changed, and its tags; then every tag of the account, with how many scores carry it. Needs the account linked.

Input parameters:

- `offset` (integer): How many scores to skip, most recent first (default 0): the answer's more gives the next.

### `read_my_score` (~68 tokens)

Open one of my scores

Open one score of the linked account as a draft, by the id list_my_scores gives: the answer is the draft and the score's summary; read_score reads its measures. Needs the account linked.

Input parameters:

- `id` (string, required): The score's id, as list_my_scores gives it.

### `save_new_score` (~87 tokens)

Save as a new score

Save the draft as a NEW score in the linked account's library (never overwrites one; a free account keeps 3 scores), under a title (default the score's own). Needs the account linked.

Input parameters:

- `draft` (string, required): The draft: the id a previous tool gave (draft).
- `title` (string): The title in the library (default the score's own).

### `update_my_score` (~85 tokens)

Save over my score

Write the draft back over the score of the linked account's library it was opened from (read_my_score), as saving in the app does: refused, nothing overwritten, when the score was saved in Cesure since. The library keeps the score's earlier version. Needs the account linked.

Input parameters:

- `draft` (string, required): The draft: the id a previous tool gave (draft).

### `organize_my_scores` (~188 tokens)

Organize my scores

Organize the scores of the linked account with tags, in ONE batch applied whole or not at all (at most 500 changes, counting the tags add creates): create_tags creates tags, add puts a tag on a score (creating the tag if the account has none of that name; names compare without case), remove takes it off, delete_unused_tags deletes tags no score carries. It never renames, deletes or changes a score, and no score's date moves. The opposite changes reverse an organizing (remove what add put, delete_unused_tags for the tags it created). Needs the account linked.

Input parameters:

- `add` (array): Tags to put on scores.
- `create_tags` (array): Tags to create, by name.
- `delete_unused_tags` (array): Tags to delete if no score carries them, by name.
- `remove` (array): Tags to take off scores.

## Diagnostics

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

## Score history

- 2026-10-24: 66
- 2026-10-23: 66
- 2026-10-22: 66
- 2026-10-21: 65
- 2026-10-20: 65
- 2026-10-19: 64
- 2026-10-18: 64
- 2026-10-17: 63
- 2026-10-16: 63
- 2026-10-15: 62
- 2026-10-14: 62
- 2026-10-13: 61
- 2026-10-12: 61

## Common questions

### What is the Cesure MCP server?

Cesure is an MCP server listed in the public MCP registry as app.cesure/cesure. Write, edit, transpose and play guitar tabs and staff notation in Cesure. This page covers its hosted endpoint (https://api.cesure.app/mcp).

### Is the Cesure MCP server safe to use?

Cesure scores 66 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 Cesure MCP server expose?

Cesure exposes 14 tools: create_score, import_score, read_score, edit_measures, transpose, and 9 more. Their descriptions and schemas cost roughly 3,344 tokens of context every time the server is loaded.

### Does the Cesure MCP server require authentication?

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

### Is the Cesure MCP server still maintained?

Cesure is still listed as active in the MCP registry. We last reached this channel on 24 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://api.cesure.app/mcp
- Website: https://cesure.app/assistants
- Changelog RSS feed: https://verifymcp.io/servers/app-cesure-cesure/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-cesure-cesure/api.json
- HTML version of this page: https://verifymcp.io/servers/app-cesure-cesure/api