← Registry

Learning Resources

everloot.app

An MCP server that searches and fetches WoW lore and Forever reference records with entity lookup and citation-ready results.

1 endpoint28 known toolsFirst detected October 19, 2026Last detected October 19, 2026

ENDPOINT 1

https://everloot.app/mcp/public

No auth detected

MCP server metadata

Name
everloot-knowledge
Version
0.8.0
Capabilities
tools.listChangedresources.listChangedcompletionsprompts.listChanged
Server instructions

Everloot answers questions about WoW: Forever. Facts built on player uploads are Everloot's data under CC BY-SA 4.0: when you show them, credit "Data from Everloot (https://everloot.app), CC BY-SA 4.0." or link https://everloot.app. Lore hits carry their own source and licence; keep them with the text. Game-file facts and Blizzard's posts stay Blizzard's.

Known tools 28

search_knowledge

Search WoW lore and Forever reference data.

Inferred read-only
get_entity

Fetch the full record behind a search hit id, for page rendering.

Inferred read-only
get_by_name

Exact full-name match (case-insensitive) for disambiguation.

Inferred read-only
search

The same search as search_knowledge, in the shape ChatGPT connectors and deep research call by name: up to 10 results, each with an id for fetch, a title and a URL to cite.

Inferred read-only
fetch

One knowledge record by the id a search result gave, whole: title, the full text in the source's words, the URL to cite, and metadata with the source, licence and date.

Inferred read-only
answer_sources

The evidence behind a question about WoW: Forever, for an answer that cites its sources: facts players observed (public after three installs agree, with the install count), curated facts, and the 2023 Warcraft Wiki (marked: may differ in Forever).

Inferred read-only
profession_path

Leveling path for one Forever profession from Everloot uploads.

Inferred read-only
recipe_thresholds

Where a Forever profession's recipes turn yellow, green and grey, inferred from the colours players' trade-skill windows showed.

Potential side effects
item_page

One Forever item: agreed name, public drop rate with kill count, and an agreed map pin.

Potential side effects
npc_page

One Forever NPC: agreed name and map pins.

Inferred read-only
object_page

One game object (a chest, herb, ore vein or fishing pool) by the id in its GUID: the items players looted from it, each with observed loot windows, windows with the item and distinct install reports.

Inferred read-only
quest_page

One Forever quest: agreed title, level, giver, turn-in, and rewards.

Inferred read-only
vendor_page

Goods one Forever vendor sells.

Inferred read-only
world_map_near

Entrances, NPCs and vendors near a spot, nearest first, with straight-line distances in yards.

Inferred read-only
entity_relations

Every typed relation of one entity, both directions: dropped by, sold by, reward from, located in (player-observed, listed where 3 installs agree, with the install count and last seen), and created by, reagent for, part of set, same icon (found in game files, unconfirmed, with the build they came from).

Inferred read-only
item_categories

Item categories from the game files (found in game files, unconfirmed, with the build): class and subclass with the client's English names and slugs, slot and quality.

Inferred read-only
talent_tree

The WoW: Forever talent trees of one class from the game files (found in game files, unconfirmed, with the build): every node with its talents, ranks, grid position, prerequisites and row gate, plus the levels talent points arrive at.

Inferred read-only
talent_plan

Decodes an Everloot talent share code (EL1-<class>-<spec>-<build>-<payload>, or a calculator link carrying one after #plan=) against the class's trees: the talents and ranks it holds, points per tree, the lowest level that can hold it, and every problem in plain words: a code made on another build, nodes the tree does not have, ranks cut back, points the rules would not place.

Inferred read-only
collection_gap

Missing items in one collection for one install.

Inferred read-only
completion_progress

What one install's characters have finished, and what is closest to done: achievements with the largest share of criteria or progress met, reputations nearest the next standing, titles known, and quests finished in a chain.

Inferred read-only
guild_board

Roster, bosses, loot, attendance, and average item level from officer uploads.

Inferred read-only
auction_history

Price history from auction scans players uploaded on purpose.

Inferred read-only
market_value

Market value, minimum buyout, historical value and units listed for one item on one WoW: Forever realm, from full auction scans players started and uploaded.

Inferred read-only
gold_ledger

Peak gold and the money events that character's own upload recorded.

Potential side effects
population

How many characters play each race, class, race and class, faction and level band on WoW: Forever, from the census of players who turned it on in the Everloot addon.

Inferred read-only
recent_changes

Newest first: Blizzard blue posts (title, author, time, a short excerpt and the link to the original), hotfix posts, and new game builds.

Inferred read-only
ecosystem_projects

Forever addons and tools from the community registry, with a board ranking: most installed, rising, most active, freshest release or best maintained.

Inferred read-only
everloot_plan

The Everloot feature catalogue: what is live, what is next, what is waiting, and which reference sites are page shapes only.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.everloot-knowledge]
url = "https://everloot.app/mcp/public"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "everloot-knowledge": {
      "type": "http",
      "url": "https://everloot.app/mcp/public"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: everloot-knowledge
Remote MCP URL: https://everloot.app/mcp/public

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "everloot-knowledge": {
      "url": "https://everloot.app/mcp/public"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "everloot-knowledge": {
      "type": "http",
      "url": "https://everloot.app/mcp/public"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "everloot-knowledge",
  "transport": "streamable-http",
  "url": "https://everloot.app/mcp/public"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.