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.

ARAM Mayhem

REMOTE · ARAMMAYHEM.COM

ARAM Mayhem builds, tiers, augments, combos and patch notes with canonical page citations.

Available components

+3 this week 71 Trust /100

Last scanned (16 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 24 Oct 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 Security74
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 403 tokens (~57/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

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

  • 16 Oct 26 +1

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

  • 14 Oct 26 +1

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

  • 12 Oct 26 +1

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

  • 11 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Oct 26 65

    First indexed and scored.

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 24 Oct 2026 · Probed https://arammayhem.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=arammayhem.com CN=WE1,O=Google Trust Services,C=US 19 Sept 2026 18 Dec 2026 ECDSA 256 ECDSA-SHA256 b228843a55a9d03f0e5b6db951000f7e
SANs: arammayhem.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 arammayhem.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
arammayhem.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://arammayhem.com/mcp Verified 200
http (plaintext) http://arammayhem.com/mcp HTTPS enforced 301 https://arammayhem.com/mcp
MCP tools · 7 exposed · ~336 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
get_augment ~42

Public augment description, rarity, availability and statistics when published. Accepts localized names or ids.

NameTypeReqDescription
augmentstringyes–
localestring––

No output schema declared.

No examples provided.

get_champion_build ~47

Measured item builds and skill orders for a champion. Accepts ids, names and aliases in all site locales.

NameTypeReqDescription
championstringyes–
localestring––

No output schema declared.

No examples provided.

get_patch_notes ~52

Site patch notes, newest by default; accepts 26.20 or 26-20. Changes may use English when a translation is unavailable.

NameTypeReqDescription
localestring––
patchstring––

No output schema declared.

No examples provided.

get_site_links ~29

Canonical ARAM Mayhem pages and the MCP setup guide.

NameTypeReqDescription
localestring––

No output schema declared.

No examples provided.

get_tier_list ~71

Champion tiers and public win/pick rates. Role uses champion class tags, not lane position. Paginated in site rank order.

NameTypeReqDescription
limitinteger––
localestring––
offsetinteger––
rolestring––
tierstring––

No output schema declared.

No examples provided.

get_top_combos ~52

Curated public combos ordered by editorial tier. These are suggestions, not measured win rates or vote rankings.

NameTypeReqDescription
championstring––
limitinteger––
localestring––

No output schema declared.

No examples provided.

search ~43

Search champion and augment names, aliases and augment descriptions across all site locales.

NameTypeReqDescription
limitinteger––
localestring––
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the ARAM Mayhem MCP server?

ARAM Mayhem is a hosted endpoint at https://arammayhem.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 · arammayhem.com

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

What is the ARAM Mayhem MCP server?

ARAM Mayhem is an MCP server listed in the public MCP registry as io.github.arammayhem/arammayhem. ARAM Mayhem builds, tiers, augments, combos and patch notes with canonical page citations. This page covers its hosted endpoint (https://arammayhem.com/mcp).

Is the ARAM Mayhem MCP server safe to use?

ARAM Mayhem scores 71 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 ARAM Mayhem MCP server expose?

ARAM Mayhem exposes 7 tools: get_tier_list, get_champion_build, get_augment, search, get_top_combos, and 2 more. Their descriptions and schemas cost roughly 336 tokens of context every time the server is loaded.

Does the ARAM Mayhem MCP server require authentication?

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

Is the ARAM Mayhem MCP server still maintained?

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