Remote MCP · Endpoint

Dnd5e MCP server

No. Dnd5e answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/dnd5e
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
209 ms
Tools exposed
48 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
D&D 5e MCP — wraps the D&D 5th Edition API (free, no auth)
Listing
From the official MCP registry (active).
Recent checks of Dnd5e
CheckedResultHandshake
1 hour agoHandshake completed209 ms
1 day agoHandshake completed141 ms
2 days agoHandshake completed171 ms
3 days agoHandshake completed120 ms
4 days agoHandshake completed54 ms
5 days agoHandshake completed105 ms
6 days agoHandshake completed391 ms
8 days agoHandshake completed71 ms
11 days agoHandshake completed71 ms
13 days agoHandshake completed639 ms
16 days agoHandshake completed827 ms
18 days agoHandshake completed84 ms
20 days agoHandshake completed64 ms
22 days agoHandshake completed55 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed57 ms
27 days agoHandshake completed80 ms
29 days agoHandshake completed50 ms

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