Remote MCP · Endpoint

Suprsonic MCP server

No. Suprsonic answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://suprsonic.ai/v1/mcp

The last check completed an MCP handshake.

Registry name
io.github.O-mega-Enterprise/suprsonic-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
222 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
One API key, dozens of capabilities for your AI agent. Zero provider auth.
Listing
From the official MCP registry (active).
Recent checks of Suprsonic
CheckedResultHandshake
2 hours agoHandshake completed222 ms
13 hours agoHandshake completed414 ms
2 days agoHandshake completed273 ms
4 days agoHandshake completed442 ms
6 days agoHandshake completed436 ms
9 days agoHandshake completed341 ms
11 days agoHandshake completed250 ms
13 days agoHandshake completed1.28 s
15 days agoHandshake completed371 ms
17 days agoHandshake completed487 ms
19 days agoHandshake completed828 ms
21 days agoHandshake completed729 ms
23 days agoHandshake completed295 ms
24 days agoHandshake completed203 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.

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