Remote MCP · Endpoint

Signal by StackEnhance MCP server

No. Signal by StackEnhance answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.stackenhance.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.gimarcus/signal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
226 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
How often 750+ e-commerce brands send marketing emails: counts, send dates, recent subject lines.
Listing
From the official MCP registry (active).
Recent checks of Signal by StackEnhance
CheckedResultHandshake
2 hours agoHandshake completed226 ms
1 day agoHandshake completed170 ms
2 days agoHandshake completed177 ms
2 days agoHandshake completed189 ms
4 days agoHandshake completed285 ms
7 days agoHandshake completed169 ms
9 days agoHandshake completed191 ms
12 days agoHandshake completed360 ms
14 days agoHandshake completed644 ms
16 days agoHandshake completed160 ms
18 days agoHandshake completed165 ms
20 days agoHandshake completed181 ms
22 days agoHandshake completed292 ms
24 days agoHandshake completed705 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 Signal by StackEnhance and makes no claim about it beyond what these checks measured.