{"id":"app.everloot/knowledge","slug":"app-everloot-knowledge","title":"Everloot: WoW Forever data","description":"World of Warcraft: Forever lore and player-observed drops, vendors, quests, professions and talents.","version":"0.9.1","publisher":{"kind":"domain","id":"everloot.app","label":"everloot.app","url":"https://everloot.app"},"website":"https://everloot.app/connect","repository":"https://github.com/Everloot/everloot","remotes":[{"type":"streamable-http","url":"https://everloot.app/mcp/public"}],"packages":[],"published":"2026-11-06","updated":"2026-11-06","status":"online","auth":"","latency_ms":3667,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"search_knowledge","title":"Search the Everloot knowledge base","description":"Searches partial names, keywords or a topic across agreed gameplay names, released zones, reference catalogs (achievements, factions, titles, quest chains, mounts, legacy perks, races, instances) and the lore archive; exact-name matches rank first. Use get_by_name only for a known exact full name. Check kind, gameVersion and sourceKind: lore is historical background, not current Forever gameplay. ","read_only":true},{"name":"get_entity","title":"Get one knowledge record by id","description":"Returns one knowledge record's summary, by the numeric id a search_knowledge or get_by_name hit gave: title, a short excerpt in the source's words, the URL to cite, source, licence and date. Gameplay metadata separates recordId from gameId and labels sourceKind, build or observed snapshot support. A game-file record carries its build and says when player uploads confirm it. Use it to read one hit ","read_only":true},{"name":"get_by_name","title":"Get records by exact name","description":"Returns records matching a known exact full name, case-insensitively, optionally narrowed by kind. Use search_knowledge for partial names or when this exact lookup misses; no exact match does not mean no gameplay facts exist. Check kind, gameVersion and sourceKind before choosing: lore is archive background and has no gameId. Pass recordId (also id) to get_entity or fetch as a string; pass the sep","read_only":true},{"name":"search","title":"Search (ChatGPT connector contract)","description":"Searches the knowledge base 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. It is the same search as search_knowledge. Use it only when the client expects the search and fetch pair; other clients should call search_knowledge. The text block is the same JSON as a string.","read_only":true},{"name":"fetch","title":"Fetch one document (ChatGPT connector contract)","description":"Returns one knowledge record in full, by the string id a search result gave: title, the full text in the source's words, the URL to cite, and metadata with the source, licence and date. It is the ChatGPT connector counterpart of get_entity, which gives only an excerpt. Use it after search, or with a search_knowledge id as a string. Give field, a JSON pointer such as /questIds, to read one value of","read_only":true},{"name":"answer_sources","title":"Evidence for a question, each piece with its source","description":"Returns cited evidence for a natural-language WoW: Forever question: observed, curated, game-file and 2023 Warcraft Wiki claims, each with source URL, licence and date. Start here for why, where or how many. Check that a claim contains the requested fact: a subject mention alone is not an answer. Observations need three agreeing installs; files stay unconfirmed with their build; archive lore may d","read_only":true},{"name":"profession_path","title":"Profession leveling path","description":"Returns a Forever profession leveling route between skill levels: agreed steps, summed reagents and estimated cost, leaving uncovered ranges as gaps. A reported recipe or orange skill range needs 3 agreeing installs. Costs use median reagent prices from at least 3 distinct installs: unscoped observations without realm, build or observation time, not one listing's price or a current realm minimum. ","read_only":true},{"name":"recipe_thresholds","title":"Recipe skill ranges","description":"Returns where one Forever profession's recipes turn yellow, green and grey, as skill ranges inferred from the colours players' trade-skill windows showed, never guessed exact numbers. A recipe appears only after 3 installs agree. Agreed reagents come with estimated cost per craft from unscoped median prices from at least 3 installs, or agreed vendor prices; missing prices stay unknown. Use it for ","read_only":true},{"name":"item_page","title":"Item page for a drop","description":"Returns one Forever item's page by item id: the agreed name, drop frequency from observed loot windows, agreed map pins, and player-reported armor, block, damage per second, stats and resistances. A number is public when one value has 3 agreeing installs in the newest build that 3 installs reported, and no competing value has 3; contested numbers are withheld. Each number states its agreeing insta","read_only":true},{"name":"npc_page","title":"NPC page","description":"Returns one Forever NPC's page by NPC id: the agreed name, the agreed map pins, and the loot windows reported for it that are not yet in the drop rates. A name or pin needs 3 installs agreeing; a pin does not require a drop. No copied spawn list. Use it to name or place an NPC when you have its id, from a search_knowledge hit, a drop row or entity_relations; use vendor_page for what an NPC sells, ","read_only":true},{"name":"object_page","title":"Game object page","description":"Returns one game object's page (a chest, herb, ore vein or fishing pool) by its entry id: the items players looted from it, each with observed loot windows, windows with the item and distinct install reports, and where players saw it on the minimap. A frequency is public after 3 install reports; a public object with nothing in its windows reads as a measured zero. The name shows once 3 installs ag","read_only":true},{"name":"quest_page","title":"Quest page","description":"Returns one Forever quest's page by quest id: agreed title, level, giver, turn-in and rewards. Each fact needs 3 installs agreeing. No copied quest text. Use it when you have a quest id, from a search_knowledge hit or entity_relations; use answer_sources for a question about the quest's story or chain, and entity_relations for what the quest rewards. Reads Everloot's public player data when connec","read_only":true},{"name":"vendor_page","title":"Vendor page","description":"Returns the goods one Forever vendor sells, by the vendor's NPC id, each with the copper price players saw. An item is listed when 3 installs agree on that item and its copper price; two agreed prices both stay listed. No copied catalog. Use it for what a vendor sells and at what price; use npc_page for where the vendor stands, entity_relations with the sold_by relation for who sells an item, and ","read_only":true},{"name":"world_map_near","title":"What is near a place on the map","description":"Lists the entrances, NPCs, vendors and treasures near a spot, nearest first, with straight-line distances in yards. Give a zone (name or map id) with x and y from 0 to 100, or an NPC id to start from where that NPC stands. Entrances come from the game files; one is confirmed once 3 installs zoned in from it. NPCs, vendors and treasures are player-observed and listed only where 3 installs agree on ","read_only":true},{"name":"entity_relations","title":"How an item, NPC, spell or quest connects to others","description":"Lists every typed relation of one entity, in both directions, grouped by relation. Player-observed relations (dropped by, sold by, reward from, located in) are listed where 3 installs agree, with the install count and last seen. Game-file relations (created by, reagent for, part of set, same icon) are found in game files, unconfirmed, with the build they came from. Ids are verified game ids from s","read_only":true},{"name":"item_categories","title":"Item categories: class, subclass, slot and quality","description":"Lists 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. With no arguments, the whole tree with item counts. With item, that item's category path. With class (a slug such as weapon or armor), and optionally subclass, slot and quality slugs, the item ids in it. Use it to place an ite","read_only":true},{"name":"talent_tree","title":"Talent trees for one class","description":"Returns 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. Node ids are the ids a share code names. Use it to read or explain a class's trees; use talent_plan to decode a share code against them, and class_races for ","read_only":true},{"name":"talent_plan","title":"Read a talent share code","description":"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. Nothing is dropped s","read_only":true},{"name":"class_races","title":"Races that can be a class, with their racial traits","description":"Lists which races can be one class in WoW: Forever, on which faction, and each race's racial traits (name, active or passive) from the game files (found in game files, unconfirmed, with the build). Narrow to one faction. Use it for whether a race can be a class, or which races a class is open to; use talent_tree for the class's talents, and population for how many play it. What each trait does is ","read_only":true},{"name":"collection_gap","title":"Owned versus missing in a collection","description":"Returns what one install still misses in one collection, against what that install uploaded as owned, grouped by source. A list row is public after 3 installs agree on the collection, the source and the item; owned is what that install uploaded. Not a Blizzard profile read and not a copied catalog. Use it for which items of a collection a player is missing; use completion_progress for achievements","read_only":true},{"name":"completion_progress","title":"Achievement, reputation, title and quest progress","description":"Shows 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. A list entry is public after 3 players (installs uploading from different addresses) report it identically. Progress shows only when that install uploaded it with the coll","read_only":true},{"name":"guild_board","title":"Guild board its officers published","description":"Returns one guild's published officer board and public progression. Use guild_search first for its exact name and realm; use guild_rankings to compare guilds in an instance. Roster, kills, loot, attendance and item level need 2 agreeing officers with verified grants. Public kills need 2 members' installs or an officer-published kill; sightings show characters the addon saw, not the game's roster. ","read_only":true},{"name":"guild_search","title":"Find a guild by the start of its name","description":"Finds the guilds whose name starts with what you typed, each with its realm, faction, how many characters the addon saw in it, and the count and date of its agreed boss kills. A guild is listed once 2 of its members' installs report the same boss, once its officers published a board, or once a character was seen in it. Guild names only, never a member's name, and a guild that asked to be hidden is","read_only":true},{"name":"guild_rankings","title":"Guild ladder for one raid or dungeon","description":"Ranks every guild with an agreed kill in one instance: by bosses killed, then by who reached its latest kill first, then by name; equal rows share a rank. A kill is a guild's once 2 of its members' installs report the same boss there, timed at the earliest report, or once its officers published it on the guild board, which carries no time. The boss list is the encounters 3 installs reported in tha","read_only":true},{"name":"auction_history","title":"Auction history for one item","description":"Returns one item's dated auction history on one Forever realm: public full-scan days used by market_value, plus separate browsing sightings. Browsing prices are the median of each install's last scan that day. A day needs 3 reporters, or, while few players upload, Everloot's own installs; preserve the own-scan label and counts. Use the full realm name (CAMWOW US1 Realm 4 PvP); a unique whole-word ","read_only":true},{"name":"market_value","title":"Forever market value for one item","description":"Returns one item's market value, historical value, minimum buyout and units listed from uploaded full auction scans on one Forever realm. Daily values are medians of reporters' values; a day needs 3 reporters from distinct addresses, or Everloot's own installs while few players upload, labelled with counts. Market value weights public days up to 14 calendar days old toward recent days, excluding t","read_only":true},{"name":"gold_ledger","title":"Gold ledger for one character","description":"Returns the peak and current gold of one character and the money events its own upload recorded: income (loot, quests, vendor and auction sales) and spending (flight paths, postage, barber, respecs, auction purchases), each install's ledger kept apart. A category with nothing recorded reads as unrecorded, not zero, and gold from other gameplay is unrecorded. The gap between recorded income and pea","read_only":true},{"name":"coverage","title":"Database coverage by zone, type and field","description":"Counts how much of WoW: Forever's database is settled or confirmed, per zone, per type and per field, as https://everloot.app/database/coverage shows it. Coverage is settled over expected, with confirmed over expected beside it; the denominator is the larger of expected and observed, and confirmed includes settled. A player-reported fact is public after three installs agree; fields one or two inst","read_only":true},{"name":"population","title":"Who plays what: population by race, class, faction and level","description":"Counts observed Forever characters by race, class, faction and level band from opt-in addon census uploads, not the whole realm population. Each character counts once. Normally counts need 10 characters, 3 installs and 3 addresses, rounded to 5, with inferable small counts hidden. While few players upload, Everloot's own installs also count on their own, though the 10-character minimum still appli","read_only":true},{"name":"recent_changes","title":"Recent official changes for WoW: Forever","description":"Returns the newest official changes for WoW: Forever, newest first: Blizzard blue posts (title, author, time, a short excerpt and the link to the original), hotfix posts, and new game builds. Excerpts only: Blizzard's post text is Blizzard's; full posts are available at their source URLs. A build's time is when Everloot first saw it, not Blizzard's release time. Use it for what Blizzard changed or","read_only":true},{"name":"ecosystem_projects","title":"WoW: Forever addons and open-source projects","description":"Lists the Forever addons and tools in the community registry, with a board ranking: most installed, rising, most active, freshest release or best maintained. Each project shows its GitHub repository, stars, latest release, last commit, whether its .toc declares a Forever interface number, and installs from Everloot uploads (counted from 3 installs; a missing count means not counted, not zero). Pro","read_only":true},{"name":"everloot_plan","title":"Everloot implementation tracker","description":"Returns the Everloot feature catalogue: what is live, what is next, what is waiting, and which reference sites are page shapes only, as the tracker that ships with the site holds it. Use it only for questions about Everloot itself, such as whether a feature exists; it holds no game data. For game facts use search_knowledge or answer_sources; for community addons use ecosystem_projects. With no arg","read_only":true}],"server_info":{"name":"everloot-knowledge","title":"Everloot","version":"0.10.0","description":"World of Warcraft: Forever facts, game-file metadata and historical lore, with sources and dates.","websiteUrl":"https://github.com/Everloot/everloot","icons":[{"src":"https://everloot.app/icon-64.png","mimeType":"image/png","sizes":["64x64"]},{"src":"https://everloot.app/icon-512.png","mimeType":"image/png","sizes":["512x512"]}]},"category":"research","tags":["web-search","finance","project"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":398149,"score":100,"indexable":true,"first_seen":"2026-10-19","stars":0,"badges":["official"],"sponsor":null,"page":"https://agentsindex.org/agents/app-everloot-knowledge/"}