Remote MCP · Endpoint

Discord MCP server

No. Discord answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/discord
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
93 ms
Tools exposed
48 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Discord MCP Pack
Listing
From the official MCP registry (active).
Recent checks of Discord
CheckedResultHandshake
1 hour agoHandshake completed93 ms
1 day agoHandshake completed128 ms
2 days agoHandshake completed76 ms
3 days agoHandshake completed66 ms
4 days agoHandshake completed50 ms
5 days agoHandshake completed111 ms
6 days agoHandshake completed97 ms
8 days agoHandshake completed71 ms
11 days agoHandshake completed54 ms
13 days agoHandshake completed1.20 s
16 days agoHandshake completed153 ms
18 days agoHandshake completed61 ms
20 days agoHandshake completed67 ms
22 days agoHandshake completed52 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed57 ms
27 days agoHandshake completed72 ms
29 days agoHandshake completed48 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 27 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 Discord and makes no claim about it beyond what these checks measured.