_ registry / mcp streamable-http · checked 10m ago

TalentAnvil

https://www.talentanvil.com

Registry code: 1bf23d7a45d54a44

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://www.talentanvil.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is TalentAnvil live?
Yes — it answered the hub's last check (checked 10m ago). It answered 99% of checks over the last 30 days.
Is TalentAnvil free to use?
Yes — the hub reached it with no key and no payment.
What tools does TalentAnvil have?
8 tools: get_character, get_talents, compare_character, get_spell, decode_build, generate_build, popular_builds, list_specs.
Is TalentAnvil safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.6%

90 days 98.8%· all time 98.8%

latency
588ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 253 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • generate a world of warcraft talent build
  • decode a talent loadout string
  • get popular raid builds for a spec
  • compare a character build with popular builds
takes → gives
text → text, data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 open 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_specs reads open 21h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_character reads unknown 5h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "realm"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Character name."
        },
        "realm": {
          "type": "string",
          "description": "Realm name or slug, e.g. \"Area 52\" or \"area-52\"."
        },
        "region": {
          "enum": [
            "us",
            "eu",
            "kr",
            "tw"
          ],
          "type": "string",
          "default": "us"
        },
        "sections": {
          "type": "array",
          "items": {
            "enum": [
              "achievement_statistics",
              "achievements",
              "appearance",
              "completed_quests",
              "dungeons",
              "equipment",
              "heirlooms",
              "hunter_pets",
              "media",
              "mounts",
              "mythic_plus",
              "pets",
              "professions",
              "pvp",
              "raids",
              "reputations",
              "stats",
              "talents",
              "titles",
              "toys"
            ],
            "type": "string"
          }
        },
        "achievement_ids": {
          "type": "array",
          "items": {
            "type": "integer"
          },
          "maxItems": 10,
          "minItems": 1,
          "description": "With the achievements section: completion status and date for each id, plus criteria progress for incomplete ones."
        },
        "raid_expansions": {
          "oneOf": [
            {
              "enum": [
                "current",
                "all"
              ],
              "type": "string"
            },
            {
              "type": "array",
              "items": {
                "type": "integer"
              }
            }
          ],
          "default": "current",
          "description": "Raid progress to include: \"current\" (default, the newest expansion), \"all\", or a list of journal expansion ids."
        },
        "achievements_limit": {
          "type": "integer",
          "default": 50,
          "maximum": 200,
          "minimum": 1,
          "description": "Page size for achievement_category."
        },
        "dungeon_expansions": {
          "oneOf": [
            {
              "enum": [
                "current",
                "all"
              ],
              "type": "string"
            },
            {
              "type": "array",
              "items": {
                "type": "integer"
              }
            }
          ],
          "default": "current",
          "description": "Dungeon progress to include: \"current\" (default, the newest expansion), \"all\", or a list of journal expansion ids."
        },
        "achievements_offset": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Skip this many completions in achievement_category (page on has_more)."
        },
        "statistics_category": {
          "type": [
            "string",
            "integer"
          ],
          "description": "With the achievement_statistics section: return the statistics in this category (name or id)."
        },
        "achievement_category": {
          "type": [
            "string",
            "integer"
          ],
          "description": "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 ambiguous name returns the matching ids."
        },
        "include_cosmetic_slots": {
          "type": "boolean",
          "default": false,
          "description": "Also include the shirt and tabard slots in equipment."
        },
        "include_inactive_loadouts": {
          "type": "boolean",
          "default": false,
          "description": "Also list every other saved loadout (all specs) as spec + talent_loadout_code."
        },
        "include_mythic_plus_seasons": {
          "type": "boolean",
          "default": false,
          "description": "Also list the ids of every M+ season the character has played."
        }
      },
      "additionalProperties": false
    }
    arguments 145 lines
  • get_talents reads unknown 5h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "class",
        "spec"
      ],
      "properties": {
        "spec": {
          "type": "string"
        },
        "class": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • compare_character reads unknown 5h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "realm"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Character name."
        },
        "realm": {
          "type": "string",
          "description": "Realm name or slug, e.g. \"Area 52\" or \"area-52\"."
        },
        "region": {
          "enum": [
            "us",
            "eu",
            "kr",
            "tw"
          ],
          "type": "string",
          "default": "us"
        },
        "difficulty": {
          "enum": [
            "normal",
            "heroic",
            "mythic",
            "mythic_plus"
          ],
          "type": "string"
        },
        "content_name": {
          "type": "string",
          "description": "Boss or dungeon name (partial match ok), or \"All Bosses\" / \"All Dungeons\". Omit for the overall build."
        }
      },
      "additionalProperties": false
    }
    arguments 41 lines
  • get_spell reads unknown 21h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "name": {
          "type": "string"
        },
        "spell_id": {
          "type": "integer"
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • decode_build reads unknown 2h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "loadout_string"
      ],
      "properties": {
        "loadout_string": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • generate_build reads unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "class",
        "spec"
      ],
      "properties": {
        "spec": {
          "type": "string"
        },
        "class": {
          "type": "string"
        },
        "include": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "hero_tree": {
          "type": "string"
        },
        "priorities": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • popular_builds reads unknown 21h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "class",
        "spec",
        "content_name"
      ],
      "properties": {
        "spec": {
          "type": "string"
        },
        "class": {
          "type": "string"
        },
        "difficulty": {
          "enum": [
            "normal",
            "heroic",
            "mythic",
            "mythic_plus"
          ],
          "type": "string"
        },
        "content_name": {
          "type": "string",
          "description": "Boss or dungeon name (partial match ok). Use \"All Bosses\" for the overall raid build, or \"All Dungeons\" for the overall M+ build."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1bf23d7a45d54a44.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1bf23d7a45d54a44/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1bf23d7a45d54a44/badge.svg)](https://brick.blue/agent/1bf23d7a45d54a44?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.