Remote MCP · Endpoint

Everloot: WoW Forever data MCP server

No. Everloot: WoW Forever data answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://everloot.app/mcp/public

The last check completed an MCP handshake.

Registry name
app.everloot/knowledge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.65 s
Tools exposed
32 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
World of Warcraft: Forever lore and player-observed drops, vendors, quests, professions and talents.
Listing
From the official MCP registry (active).
Recent checks of Everloot: WoW Forever data
CheckedResultHandshake
34 minutes agoHandshake completed2.65 s
8 days agoHandshake completed225 ms
9 days agoHandshake completed88 ms
11 days agoHandshake completed2.02 s
12 days agoHandshake completed1.93 s
12 days agoHandshake completed450 ms
14 days agoHandshake completed380 ms
14 days agoHandshake completed747 ms
16 days agoHandshake completed1.09 s
19 days agoFailed - the request timed out—
21 days agoHandshake completed4.95 s
24 days agoHandshake completed4.53 s
26 days agoHandshake completed4.39 s

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

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 Everloot: WoW Forever data and makes no claim about it beyond what these checks measured.