Remote MCP · Endpoint

AImeistrO MCP server

No. AImeistrO answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://aimeistro.com/mcp

The last check completed an MCP handshake.

Registry name
com.aimeistro/music
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
669 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Autonomous music production for AI agents with MIDI generation, QC and provenance.
Website
https://aimeistro.com/
Listing
From the official MCP registry (active).
Recent checks of AImeistrO
CheckedResultHandshake
1 day agoHandshake completed669 ms
3 days agoHandshake completed398 ms
5 days agoHandshake completed425 ms
7 days agoHandshake completed704 ms
9 days agoHandshake completed653 ms
11 days agoHandshake completed297 ms
12 days agoHandshake completed365 ms
13 days agoHandshake completed230 ms
15 days agoHandshake completed407 ms
17 days agoHandshake completed492 ms
19 days agoHandshake completed498 ms
20 days agoHandshake completed341 ms
22 days agoHandshake completed431 ms
23 days agoHandshake completed472 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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