Remote MCP · Endpoint

Ravel Edition MCP server

No. Ravel Edition answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://raveledition.com/mcp

The last check completed an MCP handshake.

Registry name
com.raveledition/ravel-edition
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
74 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Catalogue, work pages, news and orchestras of the Ravel Edition, revised editions of Ravel's works
Listing
From the official MCP registry (active).
Recent checks of Ravel Edition
CheckedResultHandshake
20 minutes agoHandshake completed74 ms
9 days agoHandshake completed74 ms
9 days agoHandshake completed464 ms
11 days agoHandshake completed83 ms
12 days agoHandshake completed91 ms
13 days agoHandshake completed59 ms
14 days agoHandshake completed515 ms
15 days agoHandshake completed76 ms
16 days agoHandshake completed463 ms
19 days agoHandshake completed81 ms
21 days agoHandshake completed176 ms
24 days agoHandshake completed59 ms
26 days agoHandshake completed81 ms
28 days agoHandshake completed77 ms

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

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 Ravel Edition and makes no claim about it beyond what these checks measured.