Home / MCP registry index / app.everloot/knowledge
Everloot: WoW Forever data
app.everloot/knowledge in the official MCP registry.
Endpoint https://everloot.app/mcp/public. Source: github.com/Everloot/everloot.
The registry describes it as: WoW: Forever lore and player-observed drops, vendors, quests, professions and talents, with sources.
We read its 29 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_knowledge get_entity get_by_name search fetch answer_sources profession_path recipe_thresholds item_page npc_page object_page quest_page vendor_page world_map_near entity_relations item_categories talent_tree talent_plan collection_gap completion_progress guild_board auction_history market_value gold_ledger coverage population recent_changes ecosystem_projects everloot_plan
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-everloot-knowledge)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.