Remote MCP · Endpoint

Sup MCP server

No. Sup answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://supwire.com/mcp

The last check completed an MCP handshake.

Registry name
com.supwire/sup
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
92 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Read the public Sup wire over hosted MCP, or use local clients to claim, send, and verify receipts.
Listing
From the official MCP registry (active).
Recent checks of Sup
CheckedResultHandshake
1 hour agoHandshake completed92 ms
1 day agoHandshake completed83 ms
2 days agoHandshake completed136 ms
3 days agoHandshake completed74 ms
4 days agoHandshake completed99 ms
5 days agoHandshake completed89 ms
6 days agoHandshake completed75 ms
9 days agoHandshake completed95 ms
12 days agoHandshake completed147 ms
14 days agoHandshake completed68 ms
16 days agoHandshake completed65 ms
18 days agoHandshake completed83 ms
20 days agoHandshake completed147 ms
22 days agoHandshake completed67 ms
24 days agoHandshake completed69 ms
26 days agoHandshake completed71 ms
27 days agoHandshake completed89 ms
29 days agoHandshake completed136 ms

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

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 Sup and makes no claim about it beyond what these checks measured.