Remote MCP · Endpoint
io.github.maginaryai/maginary-mcp MCP server
No. io.github.maginaryai/maginary-mcp answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.maginary.ai/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.maginaryai/maginary-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 258 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- AI image + video generation for agents: --flag prompt DSL, async generate/poll, x402 pay-per-use.
- Website
- https://maginary.ai/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 258 ms |
| 10 hours ago | Handshake completed | 246 ms |
| 1 day ago | Handshake completed | 257 ms |
| 2 days ago | Handshake completed | 285 ms |
| 4 days ago | Handshake completed | 238 ms |
| 4 days ago | Handshake completed | 263 ms |
| 5 days ago | Handshake completed | 261 ms |
| 6 days ago | Handshake completed | 248 ms |
| 8 days ago | Handshake completed | 270 ms |
| 11 days ago | Handshake completed | 230 ms |
| 13 days ago | Handshake completed | 234 ms |
| 16 days ago | Handshake completed | 287 ms |
| 18 days ago | Handshake completed | 270 ms |
| 20 days ago | Handshake completed | 289 ms |
| 22 days ago | Handshake completed | 235 ms |
| 24 days ago | Handshake completed | 239 ms |
| 26 days ago | Handshake completed | 276 ms |
| 27 days ago | Handshake completed | 267 ms |
| 29 days ago | Handshake completed | 250 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 io.github.maginaryai/maginary-mcp and makes no claim about it beyond what these checks measured.