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.

Clash Royale

NPM · @PIPEWORX/MCP-CLASH-ROYALE · 2 COMPONENTS

Clash Royale MCP.

+4 this week 81 Trust /100

Last scanned (12 hours ago)

Scores higher than 69% of npm servers

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-clash-royale). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 883 tokens (~58/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 +1

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

  • 29 Oct 26 77

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-clash-royale@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-clash-royale
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-clash-royale/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3612094076
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:cbd8a92d0cb6557b1cdf8f46600ab810a9ae9a39631f418e8a91288d4c3e8dfc1bc153d60ed2b0a6dc061b352af776468613495bbaa470ce965d7cae5

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~826 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
cards ~38

Clash Royale official API — complete list of all game cards: name, max level, elixir cost, rarity, type, arena, and icon URL.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

clan ~45

Clash Royale official API — full clan profile for a clan tag: name, description, type, score, member count, trophies required, and war trophies.

NameTypeReqDescription
tagstringyes–

No output schema declared.

No examples provided.

clan_current_war ~48

Clash Royale official API — current war status for a clan tag: war state, collection-day and war-day results, participants, battles remaining, and standings.

NameTypeReqDescription
tagstringyes–

No output schema declared.

No examples provided.

clan_members ~74

Clash Royale official API — paginated member list for a clan tag: each member's name, role, trophies, last active, and donations. Supports limit/after/before cursors.

NameTypeReqDescription
afterstring––
beforestring––
limitnumber––
tagstringyes–

No output schema declared.

No examples provided.

clan_search ~99

Clash Royale official API — search clans by name, locationId, min/max members, or min score. Returns matching clans with trophy counts and member totals.

NameTypeReqDescription
afterstring––
beforestring––
limitnumber––
locationIdnumber––
maxMembersnumber––
minMembersnumber––
minScorenumber––
namestring––

No output schema declared.

No examples provided.

clan_war_log ~74

Clash Royale official API — war log for a clan tag: past war seasons with participants, battles played, wins, and final standings. Supports limit/after/before cursors.

NameTypeReqDescription
afterstring––
beforestring––
limitnumber––
tagstringyes–

No output schema declared.

No examples provided.

location ~44

Clash Royale official API — details for a single location by numeric ID: name, country code, and whether it is a country or a global region.

NameTypeReqDescription
idnumberyes–

No output schema declared.

No examples provided.

locations ~36

Clash Royale official API — full list of supported location IDs (countries + global) used by ranking endpoints such as rankings_clans and rankings_players.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

player ~48

Clash Royale official API — full profile for a player tag (#2PP…): trophies, level, arena, clan, card collection, battle stats, and league ranking.

NameTypeReqDescription
tagstringyes–

No output schema declared.

No examples provided.

player_battles ~51

Clash Royale official API — recent battle log for a player tag: outcome, decks used, opponent, arena, and trophy change for each of the last ~25 battles.

NameTypeReqDescription
tagstringyes–

No output schema declared.

No examples provided.

player_upcoming_chests ~44

Clash Royale official API — upcoming chest cycle for a player tag: chest type and position index for the next chests in queue.

NameTypeReqDescription
tagstringyes–

No output schema declared.

No examples provided.

rankings_clans ~60

Clash Royale official API — top-ranked clans for a location ID (numeric): clan name, tag, score, member count, and rank position. Use global ID for worldwide rankings.

NameTypeReqDescription
limitnumber––
locationIdnumberyes–

No output schema declared.

No examples provided.

rankings_players ~61

Clash Royale official API — top-ranked players for a location ID (numeric): player name, tag, trophies, exp level, clan, and rank position. Use global ID for worldwide rankings.

NameTypeReqDescription
limitnumber––
locationIdnumberyes–

No output schema declared.

No examples provided.

tournament ~44

Clash Royale official API — tournament details for a tournament tag: name, description, max capacity, creator, current members, status, and game mode.

NameTypeReqDescription
tagstringyes–

No output schema declared.

No examples provided.

tournament_search ~60

Clash Royale official API — search open tournaments by name. Returns matching tournaments with capacity, current members, and start time.

NameTypeReqDescription
afterstring––
beforestring––
limitnumber––
namestring––

No output schema declared.

No examples provided.

Install

How do I install the Clash Royale MCP server?

Clash Royale runs locally as an npm package, launched with npx -y @pipeworx/mcp-clash-royale. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-clash-royale

# add to Claude Code
claude mcp add pipeworx-io-clash-royale -- npx -y @pipeworx/mcp-clash-royale
Common questions

What is the Clash Royale MCP server?

Clash Royale is an MCP server listed in the public MCP registry as io.github.pipeworx-io/clash-royale. Clash Royale MCP. This page covers its npm package (@pipeworx/mcp-clash-royale).

Is the Clash Royale MCP server safe to use?

Clash Royale scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Clash Royale MCP server expose?

Clash Royale exposes 15 tools: player, player_battles, player_upcoming_chests, clan, clan_members, and 10 more. Their descriptions and schemas cost roughly 826 tokens of context every time the server is loaded.

Is the Clash Royale MCP server still maintained?

Clash Royale 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.

What licence is the Clash Royale MCP server under?

Clash Royale declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.