Remote MCP · Endpoint

AImeistrO MCP server

No. AImeistrO answered an MCP handshake 6 hours ago.

UpLast checked 6 hours 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
412 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
6 hours agoHandshake completed412 ms
9 days agoHandshake completed507 ms
10 days agoHandshake completed754 ms
11 days agoHandshake completed424 ms
12 days agoHandshake completed433 ms
14 days agoHandshake completed397 ms
15 days agoHandshake completed181 ms
15 days agoHandshake completed406 ms
17 days agoHandshake completed553 ms
19 days agoHandshake completed527 ms
22 days agoHandshake completed675 ms
24 days agoHandshake completed422 ms
26 days agoHandshake completed669 ms
28 days agoHandshake completed398 ms

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

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.