Remote MCP · Endpoint

Signal by StackEnhance MCP server

No. Signal by StackEnhance answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.stackenhance.com/mcp

The last check completed an MCP handshake.

Registry name
com.stackenhance/signal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
214 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 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
1 hour agoHandshake completed214 ms
1 day agoHandshake completed158 ms
2 days agoHandshake completed361 ms
3 days agoHandshake completed564 ms
4 days agoHandshake completed156 ms
5 days agoHandshake completed178 ms
6 days agoHandshake completed173 ms
9 days agoHandshake completed181 ms
11 days agoHandshake completed156 ms
14 days agoHandshake completed211 ms
16 days agoHandshake completed180 ms
18 days agoHandshake completed190 ms
20 days agoHandshake completed1.09 s
22 days agoHandshake completed263 ms
24 days agoHandshake completed160 ms

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

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.