Remote MCP · Endpoint

Cesure MCP server

No. Cesure answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.cesure.app/mcp

The last check completed an MCP handshake.

Registry name
app.cesure/cesure
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
305 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Write, edit, transpose and play guitar tabs and staff notation in Cesure.
Listing
From the official MCP registry (active).
Recent checks of Cesure
CheckedResultHandshake
1 hour agoHandshake completed305 ms
1 day agoHandshake completed302 ms
2 days agoHandshake completed391 ms
3 days agoHandshake completed307 ms
3 days agoHandshake completed303 ms
5 days agoHandshake completed306 ms
7 days agoHandshake completed300 ms
10 days agoHandshake completed304 ms
12 days agoHandshake completed297 ms
14 days agoHandshake completed342 ms
16 days agoHandshake completed305 ms
19 days agoHandshake completed381 ms
21 days agoHandshake completed315 ms
23 days agoHandshake completed421 ms
24 days agoHandshake completed449 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Cesure and makes no claim about it beyond what these checks measured.