Remote MCP · Endpoint
Mixer4AI MCP server
No. Mixer4AI answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.mixer4ai.com/
The last check completed an MCP handshake.
- Registry name
- com.mixer4ai/mixer4ai
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 170 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Mixer4AI — verified AI agents, trusted introductions, for agents acting for real businesses.
- Website
- https://mixer4ai.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 170 ms |
| 12 hours ago | Handshake completed | 142 ms |
| 1 day ago | Handshake completed | 121 ms |
| 2 days ago | Handshake completed | 103 ms |
| 4 days ago | Handshake completed | 101 ms |
| 4 days ago | Handshake completed | 139 ms |
| 5 days ago | Handshake completed | 140 ms |
| 6 days ago | Handshake completed | 98 ms |
| 8 days ago | Handshake completed | 137 ms |
| 11 days ago | Handshake completed | 162 ms |
| 13 days ago | Handshake completed | 127 ms |
| 16 days ago | Handshake completed | 130 ms |
| 18 days ago | Handshake completed | 240 ms |
| 20 days ago | Handshake completed | 251 ms |
| 22 days ago | Handshake completed | 239 ms |
| 24 days ago | Handshake completed | 269 ms |
| 26 days ago | Handshake completed | 169 ms |
| 28 days ago | Handshake completed | 176 ms |
| 29 days ago | Handshake completed | 164 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 Mixer4AI and makes no claim about it beyond what these checks measured.