Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TalentAnvil

REMOTE · WWW.TALENTANVIL.COM

WoW talent builds for every class and spec: valid, importable loadout strings plus popular builds.

+1 this week 83 Trust /100

Last scanned (1 hour ago)

Scores higher than 87% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1368 tokens (~171/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 48% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
  • 29 Oct 26 +7
    • Authorization: unverified → partial ▲ security
  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://www.talentanvil.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=talentanvil.com CN=WE1,O=Google Trust Services,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 d472614a0061d2c00ea9e779de40c4ac
SANs: talentanvil.com, *.talentanvil.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.talentanvil.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
talentanvil.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.talentanvil.com/mcp Verified 200
http (plaintext) http://www.talentanvil.com/mcp HTTPS enforced 301 https://www.talentanvil.com/mcp
MCP tools · 8 exposed · ~1,368 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_character ~196

Compare a live character's active talent loadout with the most popular build for their spec (Warcraft Logs raid kills and the Mythic+ leaderboards, current raid tier). By default it compares against the spec's overall build (All Dungeons or All Bosses, the best-sampled first); pass content_name and/or difficulty to pick a dungeon or boss. Returns both loadout strings and hero trees, plus the differences: talents only the character has, talents only the popular build has, and rank and choice differences.

NameTypeReqDescription
content_namestring–Boss or dungeon name (partial match ok), or "All Bosses" / "All Dungeons". Omit for the overall build.
difficultystring––
namestringyesCharacter name.
realmstringyesRealm name or slug, e.g. "Area 52" or "area-52".
regionstring––

No output schema declared.

No examples provided.

decode_build ~40

Decode a loadout string into its class/spec and the selected talents, each with its rank and max_ranks.

NameTypeReqDescription
loadout_stringstringyes–

No output schema declared.

No examples provided.

generate_build ~92

Produce a valid, importable loadout string for a class/spec. Provide talents to include (by name or id), an optional hero tree, and priority talents to fill remaining points. The solver enforces prerequisites, gates, and budgets.

NameTypeReqDescription
classstringyes–
hero_treestring––
includearray––
prioritiesarray––
specstringyes–

No output schema declared.

No examples provided.

get_character ~683

Look up a live World of Warcraft character from Blizzard's armory: profile summary (class, spec, level, item level, guild, faction) plus the sections you ask for — gear, talents, stats, M+, raid and dungeon progress, professions, PvP, achievements, collections, and more. Defaults to equipment, talents, stats, mythic_plus. Talents return only the active spec's active loadout: hero tree, the importable talent_loadout_code (pass it to decode_build), and each talent as {node_id, talent_id, name, rank}; set include_inactive_loadouts for every other saved loadout's code. Equipment is compact: equipped item level, then per item slot, name, item level, track (name_description), stats, gems, enchants, spell/proc text, set and bonus_list; set bonuses sit once in equipped_item_sets. mythic_plus returns the current season's rating and the best run per dungeon. raids and dungeons cover the current expansion only, newest release first and Mythic → Raid Finder; use raid_expansions / dungeon_expansions for others. achievements returns a summary (total points, completed count, recent completions, per-category progress); use achievement_category (paged with achievements_limit / achievements_offset) to list completions in one category, or achievement_ids to check specific achievements with criteria progress. achievement_statistics lists its categories; use statistics_category for the values. pets is name/species/level/quality; completed_quests is quest ids. Results are kept under ~20k tokens: anything left out to fit is listed in truncated_sections with the request that fetches it.

NameTypeReqDescription
achievement_categorystring|integer–With the achievements section: list completed achievements (id, name, completed date, points) in this category and its subcategories, newest first. A category name (e.g. "Midnight Raid") or id; an am…
achievement_idsarray–With the achievements section: completion status and date for each id, plus criteria progress for incomplete ones.
achievements_limitinteger–Page size for achievement_category.
achievements_offsetinteger–Skip this many completions in achievement_category (page on has_more).
dungeon_expansions––Dungeon progress to include: "current" (default, the newest expansion), "all", or a list of journal expansion ids.
include_cosmetic_slotsboolean–Also include the shirt and tabard slots in equipment.
include_inactive_loadoutsboolean–Also list every other saved loadout (all specs) as spec + talent_loadout_code.
include_mythic_plus_seasonsboolean–Also list the ids of every M+ season the character has played.
namestringyesCharacter name.
raid_expansions––Raid progress to include: "current" (default, the newest expansion), "all", or a list of journal expansion ids.
realmstringyesRealm name or slug, e.g. "Area 52" or "area-52".
regionstring––
sectionsarray––
statistics_categorystring|integer–With the achievement_statistics section: return the statistics in this category (name or id).

No output schema declared.

No examples provided.

get_spell ~69

Get the current Blizzard details for a spell — name and full effect description — by spell id (from get_talents) or by name. Data is refreshed daily, so it reflects the live patch rather than stale training data.

NameTypeReqDescription
namestring––
spell_idinteger––

No output schema declared.

No examples provided.

get_talents ~82

List the selectable talents for a class/spec (id, name, effect description, spell id, sub-tree, hero tree, choices). Call this before generate_build so you know the talent names and what each one does. Use get_spell for the full, freshest detail on any spell id.

NameTypeReqDescription
classstringyes–
specstringyes–

No output schema declared.

No examples provided.

list_specs ~24

List every class/spec available, with the slugs used by the other tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

popular_builds ~182

Get the importable loadout that players actually ran to kill a raid boss (or clear an M+ dungeon), aggregated from Warcraft Logs and the M+ leaderboards, for a class/spec. Pass a boss/dungeon name, or a general all-round build for the whole content: "All Bosses" for a raid (set difficulty to normal/heroic/mythic), or "All Dungeons" for M+ (set difficulty to "mythic_plus"). Returns the modal build string, sample size, and per-choice pick frequencies.

NameTypeReqDescription
classstringyes–
content_namestringyesBoss or dungeon name (partial match ok). Use "All Bosses" for the overall raid build, or "All Dungeons" for the overall M+ build.
difficultystring––
specstringyes–

No output schema declared.

No examples provided.

Install

How do I install the TalentAnvil MCP server?

TalentAnvil is a hosted endpoint at https://www.talentanvil.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.talentanvil.com

# add to Claude Code
claude mcp add --transport http com-talentanvil-talentanvil 'https://www.talentanvil.com/mcp'
Common questions

What is the TalentAnvil MCP server?

TalentAnvil is an MCP server listed in the public MCP registry as com.talentanvil/talentanvil. WoW talent builds for every class and spec: valid, importable loadout strings plus popular builds. This page covers its hosted endpoint (https://www.talentanvil.com/mcp).

Is the TalentAnvil MCP server safe to use?

TalentAnvil scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the TalentAnvil MCP server expose?

TalentAnvil exposes 8 tools: list_specs, get_talents, generate_build, decode_build, popular_builds, and 3 more. Their descriptions and schemas cost roughly 1,368 tokens of context every time the server is loaded.

Does the TalentAnvil MCP server require authentication?

No. We connected to TalentAnvil without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the TalentAnvil MCP server still maintained?

TalentAnvil is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.