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.

Runekist

REMOTE · RUNEKIST.COM · SCANNED SEP 28

Total Battle clan insights, chest rewards, and stacking calculations through Runekist.

Available components

72 Trust /100
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 Security83
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2188 tokens (~91/item across 24 items; 24 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 24 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
Install

How do I install the Runekist MCP server?

Runekist is a hosted endpoint at https://runekist.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 · runekist.com

# add to Claude Code
claude mcp add --transport http com-runekist-runekist 'https://runekist.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-runekist-runekist": {
      "url": "https://runekist.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-runekist-runekist": {
      "type": "http",
      "url": "https://runekist.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-runekist-runekist]
url = "https://runekist.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-runekist-runekist": {
      "type": "remote",
      "url": "https://runekist.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-runekist-runekist --url 'https://runekist.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-runekist-runekist:
    url: "https://runekist.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-runekist-runekist": {
      "Transport": "http",
      "Url": "https://runekist.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-runekist-runekist -t streamable-http -u 'https://runekist.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-runekist-runekist": {
      "type": "http",
      "url": "https://runekist.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1
    • Tool “find_players” rewrote its description, which is the text the model reads security
    • Tool “get_chest_reward_insights” rewrote its description, which is the text the model reads security
    • Tool “get_clan_content” rewrote its description, which is the text the model reads security
    • Tool “get_context” rewrote its description, which is the text the model reads security
    • Tool “get_insight” rewrote its description, which is the text the model reads security
    • Tool “get_insight_options” rewrote its description, which is the text the model reads security
    • Tool “get_my_progress” rewrote its description, which is the text the model reads security
    • Tool “legacy_stacking” rewrote its description, which is the text the model reads security
    • Tool “list_periods” rewrote its description, which is the text the model reads security
    • Schema quality: 1098 → 1303 ▼ functional
    • Schema quality: fair → good functional
    • New tool “get_game_calendar” functional
    • “get_insight” added an optional parameter “at” cosmetic
    • “get_insight” added an optional parameter “view” cosmetic
  • 26 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 25 Sept 26 +30
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 39

    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 28 Sept 2026 · Probed https://runekist.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=runekist.com CN=YE1,O=Let's Encrypt,C=US 22 Aug 2026 20 Nov 2026 ECDSA 256 ECDSA-SHA384 5903765322a71b56f24bb1c02db8d0c7073
SANs: *.runekist.com, runekist.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of runekist.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
runekist.com. present 2371 13 Verified
runekist.com. Verified address RRset verified with the apex keys
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://runekist.com/mcp Verified 200
http (plaintext) http://runekist.com/mcp HTTPS enforced 301 https://runekist.com/mcp
MCP tools · 24 exposed · ~2,188 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
attribute_cp_receipt ~58

Credit a pending silver receipt after sender review. Required scopes: cp:write

NameTypeReqDescription
clan_idstringyes–
reasonstringyes–
receipt_idstringyes–
sender_progress_idstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

dismiss_cp_report ~50

Dismiss an unhandled report with an audit reason. Required scopes: cp:write

NameTypeReqDescription
clan_idstringyes–
reasonstringyes–
source_idstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

find_players ~44

Find bounded player candidates in one clan. Similar names remain separate candidates. Required scopes: insights:read

NameTypeReqDescription
clan_idstringyes–
querystring––
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

get_chest_reward_insights ~52

Read aggregate observed chest rewards with denominators and coverage. This is not official game probability. Required scopes: rewards:read

NameTypeReqDescription
clan_idstringyes–
filtersobject––
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

get_clan_content ~46

Read visible rules, announcements, events and the caller's outstanding tasks. Required scopes: content:read

NameTypeReqDescription
clan_idstringyes–
kindstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

get_context ~35

List authorized clans, roles, locale, timezone, and the configured UTC Total Battle game-day reset. Required scopes: context:read

Input schema present but exposes no named parameters.

NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

get_cp_balance ~46

Read period-independent personal silver balances, or all clan balances for a superior. Required scopes: cp:read

NameTypeReqDescription
allboolean––
clan_idstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

get_cp_history ~60

Read a bounded page of silver entries for one game progress ID. Required scopes: cp:read

NameTypeReqDescription
clan_idstringyes–
pageinteger––
page_sizeinteger––
progress_idstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

get_game_calendar ~117

Read bounded occurrences of the configured global game schedule, including historical UTC start/end bounds. This is not observed game evidence or clan-authored content. Officer access required. Discover cycle filters in cycle_options; windows are at most 90 days. Required scopes: context:read

NameTypeReqDescription
calendar_kindstring––
clan_idstringyes–
cycle_filtersarray––
fromstringyes–
pageinteger––
page_sizeinteger––
tostringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

get_insight ~825

Read officer-authorized Insights. Requirements: legacy period_id returns full detail; detail=summary enables bounded score pages. Example: family=requirements, detail=summary, period_selector=last_completed, period_count=4, aggregate=player, sort=total_points, page_size=10. Or use period_id / period_ids (up to 12), membership_scope=period_participants or current_roster, member_search, exact player_ids or player_names (same-name identities stay separate), sort, direction, page. Completed means ends_at has passed in UTC. Preserved scores use the explicitly pinned historical publication. Ready scores match current inputs; finalized scores use the last published historical snapshot with stat_version_id and snapshot_completed_at. Missing/stale stats remain unavailable, not zero. Raw total_points comes from that snapshot and differs from fine-adjusted rank_points; live rules, fines and identity presentation may still change. Other family filters: chests (period_id, search, selection, sort=chest_count|total_points, direction, page, page_size; selected total_points covers selected chest types and default order remains chest_count); resources and dragon_coins (period_id, from, to, resource where applicable, search, summary_page, activity_page, page_size, ledger_search, ledger_page, ledger_page_size); forest_essence (period_id, from, to, search, summary_page, activity_page, page_size); titles (period_id, search, title_id, member_search, member_page, member_page_size); gold_pass (status, event_number, search, sort=nickname|first_observed_with_gold_pass_at|first_observed|state, direction, page, page_size; timestamp nulls last in both directions; state order with, without, unknown ascending); roster (default events: search, sort, direction, page, page_size; view=periods adds ISO-8601 at and sort=joined_at|playerName); vaults (period_id, day, interval, player, evidence_page, evidence_page_size, search, sort, page, page_size); journal (period_id, page, page_size); ancients (perio…

NameTypeReqDescription
activity_pageinteger––
aggregatestring––
atstring––
clan_idstringyes–
daystring––
detailstring––
directionstring––
event_idstring––
event_numberinteger––
evidence_pageinteger––
evidence_page_sizeinteger––
familystringyes–
fromstring––
intervalstring––
ledger_pageinteger––
ledger_page_sizeinteger––
ledger_searchstring––
member_pageinteger––
member_page_sizeinteger––
member_searchstring––
membership_scopestring––
min_failed_periodsinteger––
pageinteger––
page_sizeinteger––
period_countinteger––
period_idstring––
period_idsarray––
period_selectorstring––
playerstring––
player_idsarray––
player_namesarray––
resourcestring––
rule_idstring––
searchstring––
selectionarray––
sortstring––
statusstring––
summary_pageinteger––
title_idstring––
tostring––
viewstring––
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

get_insight_options ~52

List authorized periods, report families, resources and player filter candidates. Required scopes: insights:read

NameTypeReqDescription
clan_idstringyes–
familystring––
searchstring––
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

get_my_progress ~44

Read the caller's personal progress, requirements and collection freshness. Required scopes: personal:read

NameTypeReqDescription
clan_idstringyes–
period_idstring––
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

legacy_stacking ~53

List, load or calculate legacy stacking. Beta layouts and writes are rejected. Required scopes: stacking:calculate

NameTypeReqDescription
inputobject––
layout_idstring––
operationstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

list_cp_collector_costs ~52

Read recent collector runs with itemized base, caravan, and report credit reservations and settlements. Required scopes: cp:read

NameTypeReqDescription
clan_idstringyes–
limitinteger––
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

list_cp_reports ~52

Read a bounded page of unhandled CP reports for clan leadership. Required scopes: cp:read

NameTypeReqDescription
clan_idstringyes–
pageinteger––
page_sizeinteger––
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

list_periods ~35

List bounded Runekist periods without creating period rows. Required scopes: context:read

NameTypeReqDescription
clan_idstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

post_cp_run ~88

Post a named selection of CP reports after reviewing its exact preview. Required scopes: cp:write

NameTypeReqDescription
clan_idstringyes–
cp_denominatorstringyes–
idempotency_keystringyes–
namestringyes–
occurred_atstring––
silver_numeratorstringyes–
source_idsarrayyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

post_manual_cp_run ~99

Post a historical manual CP run with explicit progress IDs and a UTC date. Required scopes: cp:write

NameTypeReqDescription
clan_idstringyes–
cp_denominatorstringyes–
idempotency_keystringyes–
journal_entry_uuidstring––
namestringyes–
occurred_atstringyes–
participantsarrayyes–
silver_numeratorstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

preview_cp_run ~62

Preview exact member charges for selected ready report sources without posting. Required scopes: cp:read

NameTypeReqDescription
clan_idstringyes–
cp_denominatorstringyes–
silver_numeratorstringyes–
source_idsarrayyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

reconcile_manual_cp_run ~58

Link a historical manual CP charge to a subsequently observed Journal UUID without charging again. Required scopes: cp:write

NameTypeReqDescription
clan_idstringyes–
journal_uuidstringyes–
manual_source_idstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

record_cp_payment ~66

Record exact received silver for a game progress ID. Required scopes: cp:write

NameTypeReqDescription
amountstringyes–
clan_idstringyes–
idempotency_keystringyes–
progress_idstringyes–
reasonstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

reverse_cp_run ~49

Reverse a posted CP run with an audit reason. Required scopes: cp:write

NameTypeReqDescription
batch_idstringyes–
clan_idstringyes–
reasonstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

set_cp_options ~69

Set default-off CP ledger and independent collector addons where permitted. Required scopes: cp:write

NameTypeReqDescription
caravans_enabledboolean––
caravans_sincestring––
clan_idstringyes–
enabledbooleanyes–
reports_enabledboolean––
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

transfer_cp_silver ~76

Transfer exact silver between two game progress IDs. Required scopes: cp:write

NameTypeReqDescription
amountstringyes–
clan_idstringyes–
from_progress_idstringyes–
idempotency_keystringyes–
reasonstringyes–
to_progress_idstringyes–
NameTypeReqDescription
coverageobjectyes–
data–yes–
effective_scopeobjectyes–
generated_atstringyes–
provenanceobjectyes–
schema_versionstringyes–

No examples provided.

Common questions

What is the Runekist MCP server?

Runekist is an MCP server listed in the public MCP registry as com.runekist/runekist. Total Battle clan insights, chest rewards, and stacking calculations through Runekist. This page covers its hosted endpoint (https://runekist.com/mcp).

Is the Runekist MCP server safe to use?

Runekist scores 72 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 Runekist MCP server expose?

Runekist exposes 24 tools: attribute_cp_receipt, dismiss_cp_report, find_players, get_chest_reward_insights, get_clan_content, and 19 more. Their descriptions and schemas cost roughly 2,188 tokens of context every time the server is loaded.

Does the Runekist MCP server require authentication?

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

Is the Runekist MCP server still maintained?

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