Production-grade MCP server and AI tools for the Godot engine
Nothing to run from here
Everloot: WoW Forever data is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
29
tools declared
remote
at its publisher
—
calls last 7d
What it does
WoW: Forever lore and player-observed drops, vendors, quests, professions and talents, with sources.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http everloot-wow-forever-data-mcp https://everloot.app/mcp/public
# 2 — ask your agent for something these tools do
# search_knowledge, get_entity, get_by_name and 26 more
Everloot: WoW Forever data costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
EVAll 1 server
everloot1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http everloot-wow-forever-data-mcp https://everloot.app/mcp/publicReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
29 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search WoW lore and Forever reference data. Exact-name matches rank first. Every hit carries its source and licence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look up: names, questions, keywords. Question words are ignored. |
| kind | string | no | Narrow to one record kind. |
| version | string | no | Narrow to one game version. |
| limit | integer | no | — |
Fetch the full record behind a search hit id, for page rendering.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Record id from a search_knowledge hit. |
Exact full-name match (case-insensitive) for disambiguation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Full record name. |
| kind | string | no | Narrow to one record kind. |
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. The text block is the same JSON as a string.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look up: names, questions, keywords. Question words are ignored. |
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. The text block is the same JSON as a string.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | An id from a search result. |
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). Every piece carries a claim, its source URL, licence and date. Returns evidence rather than prose. Further-reading links are search URLs on other sites;
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The question, with names spelled as in the game. |
| limit | integer | no | Most lore and curated pieces. |
Leveling path for one Forever profession from Everloot uploads. A step exists only after 3 installs agree: on a reported recipe, or on the recipe colours that make it orange (a guaranteed skill-up), starting at the trainer's required rank. Gold exists only after 3 price uploads agree. No copied guide. Reads Everloot's current authorized public corpus when connected. Missing or unavailable data is
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profession | string | yes | Profession name, such as Alchemy. |
| fromSkill | integer | no | Skill the character has now. |
| toSkill | integer | yes | Skill to stop at. Must be above fromSkill. |
Where a Forever profession's recipes turn yellow, green and grey, inferred from the colours players' trade-skill windows showed. A recipe appears only after 3 installs agree, as ranges, never guessed exact numbers. Agreed reagents come with an estimated cost per craft when every reagent has an agreed price. Reads Everloot's current public corpus.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profession | string | yes | Profession name, such as Alchemy. |
| recipe | string | no | Optional part of a recipe name to narrow the list. |
One Forever item: agreed name, public drop rate with kill count, and an agreed map pin. A rate is public after 3 installs kill the source. A name or pin needs 3 installs agreeing. No Wowhead rows. Reads Everloot's current authorized public corpus when connected. Missing or unavailable data is reported explicitly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itemId | integer | yes | Item id from a drop row. |
One Forever NPC: agreed name and map pins, and loot windows reported but not yet in the rates. A name or pin needs 3 installs agreeing. The pin does not require a drop. No copied spawn list. Reads Everloot's current authorized public corpus when connected. Missing or unavailable data is reported explicitly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| npcId | integer | yes | NPC id. |
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. A frequency is public after 3 install reports; a public object with nothing in its windows reads as a measured zero. The name is shown when 3 installs agree on it. Reads Everloot's current authorized
| Parameter | Type | Required | Notes |
|---|---|---|---|
| objectId | integer | yes | The object's entry id, as in /database/objects/1731. |
One Forever quest: agreed title, level, giver, turn-in, and rewards. Each fact needs 3 installs agreeing. No copied quest text. Reads Everloot's current authorized public corpus when connected. Missing or unavailable data is reported explicitly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| questId | integer | yes | Quest id. |
Goods one Forever vendor sells. An item is listed when 3 installs agree on that item and its copper price. Two agreed prices both stay listed. No copied catalog. Reads Everloot's current authorized public corpus when connected. Missing or unavailable data is reported explicitly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vendorNpcId | integer | yes | Vendor NPC id. |
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 the positi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | no | Zone name or map id, such as Elwynn Forest or 1429. Needs x and y. |
| x | number | no | Across the zone map, 0 (west) to 100 (east). |
| y | number | no | Down the zone map, 0 (north) to 100 (south). |
| npcId | integer | no | Start from this NPC's agreed position instead of a zone and x, y. |
| radius | number | no | Search radius in yards. |
| limit | integer | no | Most results per list. |
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). Ids are the game's own. Reads Everloot's current authorized public corpus and the committed cli
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | What the id names. A zone is a UiMap id, as on /map. |
| id | integer | yes | The game's id for it, such as item 19019. |
| rel | string | no | Only this relation. |
| direction | string | no | from: what this entity points to (an item's sources). to: what points at it (what an NPC drops). Default both. |
| limit | integer | no | Most lines per relation. |
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 items in it. Ids only: item names come from
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item | integer | no | An item id: answers its class, subclass, slot and quality. |
| class | string | no | Class slug, such as weapon, armor, consumable or trade-goods. |
| subclass | string | no | Subclass slug or number within the class, such as one-handed-swords or cloth. |
| slot | string | no | Slot slug, such as head, chest, one-hand or trinket. |
| quality | string | no | poor, common, uncommon, rare, epic, legendary, artifact or heirloom. |
| limit | integer | no | Most items listed. |
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. Narrow to one tree by name. The calculator is at /tools/talents/<class>.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| class | string | yes | Class slug. |
| tree | string | no | One tree by name, such as Arcane. Without it, every tree. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The share code, or a link that carries one. |
Missing items in one collection for one install. 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. Reads Everloot's current authorized public corpus when connected. Missing or unavailable data is reported explicitly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| collection | string | yes | Collection name, such as Mounts. |
| ownerInstallId | string | yes | Install id whose owned upload to compare. |
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 is shown only when that install uploaded it with the collec
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ownerInstallId | string | yes | Install id whose completion upload to read. |
| characterKey | string | no | One character's 8-digit key from the upload, when the install has several. |
One guild's roster, bosses killed, loot awarded, raid attendance and average item level, as that guild's own officers chose to publish them. Only uploads from officers holding a verified grant for the guild count, and a figure is public after 2 of them agree. Names are in-game character names, never accounts or real-world identities. A character's owner can opt out, and an opted-out character is l
| Parameter | Type | Required | Notes |
|---|---|---|---|
| guildName | string | yes | Guild name. |
| realm | string | yes | Realm name. |
Price history from auction scans players uploaded on purpose. A day is public after 3 installs scanned that item on that realm. Copper is the median. Reads Everloot's current authorized public corpus when connected. Missing or unavailable data is reported explicitly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| realm | string | yes | Realm name. |
| itemId | integer | yes | Item id. |
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. A day is public after 3 reporters (distinct upload addresses) scanned the item; values are medians, thin days and outlier days are left out of the market value. Market value weights the last 14 public days, historical is the median of 60. Mis
| Parameter | Type | Required | Notes |
|---|---|---|---|
| realm | string | yes | Realm name. |
| itemId | integer | yes | Item id. |
Peak gold and the money events that character's own upload recorded. Loot, quests, vendors, and auction sales stay on the money line. Gameplay stays on its own line. A missing line is unrecorded. The difference is not called bought and is not a ban. Installs are not merged. No scan of a player who did not upload. Reads Everloot's current authorized public corpus when connected. Missing or unavaila
| Parameter | Type | Required | Notes |
|---|---|---|---|
| character | string | yes | Character name. |
| realm | string | yes | Realm name. |
How much of WoW: Forever's database is settled or confirmed, and which reported fields need more agreeing installs. The same counts and reported lists as https://everloot.app/database/coverage, as text, per zone, per type and per field: coverage = settled / expected, with confirmed / expected beside it; the denominator is max(expected, observed). A player-reported fact needs three agreeing install
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | integer | no | Released UiMap zone id, such as 1429 for Elwynn Forest. Omit for all released zones. |
| type | string | no | Coverage type. Omit for all types. |
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. Each character counts once. A count shows only when it covers at least 10 characters reported by at least 3 installs from at least 3 addresses, rounded to the nearest 5, and a count that could be worked out from the others is hidden t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| race | string | no | A race, such as Gnome, Night Elf or Undead. |
| class | string | no | A class, such as Priest. |
| faction | string | no | Alliance or Horde. |
| window | string | no | week: active in the last 7 days. launch: seen since launch. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | string | no | posts (blue posts), hotfixes, builds, or all. |
| game | string | no | Narrow to one game. |
| limit | integer | no | — |
Forever addons and tools from 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). Projects ar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| board | string | no | installed, rising, active, release, maintained, or all (A to Z). |
| forever_ready_only | boolean | no | Only projects whose .toc lists a Forever interface number. |
| limit | integer | no | — |
The Everloot feature catalogue: what is live, what is next, what is waiting, and which reference sites are page shapes only.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Everloot: WoW Forever data or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.8.0 · scanned 22 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest5d2159b4a1cd46aa3c798ea8d7a42fc751f239036964c2410ebcd1a3cb8c064f
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_knowledge | no tags | |
| get_entity | untrusted-input | untrusted-input: keyword "fetch" |
| get_by_name | no tags | |
| search | no tags | |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
| answer_sources | no tags | |
| profession_path | no tags | |
| recipe_thresholds | no tags | |
| item_page | no tags | |
| npc_page | no tags | |
| object_page | no tags | |
| quest_page | no tags | |
| vendor_page | no tags | |
| world_map_near | no tags | |
| entity_relations | no tags | |
| item_categories | no tags | |
| talent_tree | no tags | |
| talent_plan | no tags | |
| collection_gap | no tags | |
| completion_progress | no tags | |
| guild_board | no tags | |
| auction_history | no tags | |
| market_value | no tags | |
| gold_ledger | no tags | |
| coverage | no tags | |
| population | no tags | |
| recent_changes | no tags | |
| ecosystem_projects | no tags | |
| everloot_plan | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest5d2159b4a1cd46aa
Scanned2026-10-22
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.8.0.
0.8.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Everloot: WoW Forever data can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.