Remote MCP · Endpoint

Slack_connect MCP server

No. Slack_connect answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/slack_connect/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/slack_connect
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
60 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Slack MCP Pack
Website
https://pipeworx.io/packs/slack_connect
Repository
https://github.com/pipeworx-io/mcp-slack_connect
Listing
From the official MCP registry (active).
Recent checks of Slack_connect
CheckedResultHandshake
1 hour agoHandshake completed60 ms
2 days agoHandshake completed51 ms
4 days agoHandshake completed52 ms
5 days agoHandshake completed96 ms
7 days agoHandshake completed46 ms
8 days agoHandshake completed181 ms
9 days agoHandshake completed60 ms
12 days agoHandshake completed46 ms
14 days agoHandshake completed49 ms
15 days agoHandshake completed96 ms
17 days agoHandshake completed57 ms
18 days agoHandshake completed36 ms
19 days agoHandshake completed34 ms
20 days agoHandshake completed42 ms
20 days agoHandshake completed53 ms
22 days agoHandshake completed56 ms
23 days agoHandshake completed42 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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