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.

dev.workers.3labsio.kingofthehill/king-of-the-hill

REMOTE · KINGOFTHEHILL.3LABSIO.WORKERS.DEV

x402 game: take the crown, each take raises the next price 1.5x. hill_status is free.

0 this week 74 Trust /100

Last scanned (1 hour ago)

Scores higher than 66% of remote servers

Reachable. Last reached 23 Oct 2026.

Category Crypto and Web3

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 Security46
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 231 tokens (~115/item across 2 items; 2 tools + 0 resources), lean.Pass
  • 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 17 Aug 26 0
    • Tool “hill_take” rewrote its description, which is the text the model reads security
    • Schema quality: 69 → 115 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • “hill_take” added an optional parameter “url” cosmetic
  • 16 Aug 26 0

    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 23 Oct 2026 · Probed https://kingofthehill.3labsio.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=3labsio.workers.dev CN=WE1,O=Google Trust Services,C=US 8 Oct 2026 6 Jan 2027 ECDSA 256 ECDSA-SHA256 85a9ac310c9eadde131aaf8cead3212d
SANs: 3labsio.workers.dev, *.3labsio.workers.dev
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 kingofthehill.3labsio.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. 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://kingofthehill.3labsio.workers.dev/mcp Verified 200
http (plaintext) http://kingofthehill.3labsio.workers.dev/mcp Served over HTTP 200
MCP tools · 2 exposed · ~193 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
hill_status ~39

Free. Who holds the crown, what it costs to take it right now, how much has been raised, and each holder's share of the board.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hill_take ~154

Take the crown at the current price, paid in USDC on Base via x402. The price rises 1.5x for the next challenger, and your territory is your share of everything ever paid — a ratio that SHRINKS every time anyone else pays. Money paid is not returned: no payout, resale, dividend or claim on the pot, and later takes do not pay earlier holders. You are buying a place on a board. Returns payment instructions when unpaid.

NameTypeReqDescription
namestring–Display name for the board, max 32 chars
urlstring–Optional https link your territory points at, max 200 chars, rendered nofollow. Paying again is the only way to change it.

No output schema declared.

No examples provided.

Install

How do I install the dev.workers.3labsio.kingofthehill/king-of-the-hill MCP server?

dev.workers.3labsio.kingofthehill/king-of-the-hill is a hosted endpoint at https://kingofthehill.3labsio.workers.dev/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 · kingofthehill.3labsio.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-3labsio-kingofthehill-king-of-the-hi 'https://kingofthehill.3labsio.workers.dev/mcp'
Common questions

What is the dev.workers.3labsio.kingofthehill/king-of-the-hill MCP server?

dev.workers.3labsio.kingofthehill/king-of-the-hill is an MCP server listed in the public MCP registry as dev.workers.3labsio.kingofthehill/king-of-the-hill. x402 game: take the crown, each take raises the next price 1.5x. hill_status is free. This page covers its hosted endpoint (https://kingofthehill.3labsio.workers.dev/mcp).

Is the dev.workers.3labsio.kingofthehill/king-of-the-hill MCP server safe to use?

dev.workers.3labsio.kingofthehill/king-of-the-hill scores 74 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 dev.workers.3labsio.kingofthehill/king-of-the-hill MCP server expose?

dev.workers.3labsio.kingofthehill/king-of-the-hill exposes 2 tools: hill_status, hill_take. Their descriptions and schemas cost roughly 193 tokens of context every time the server is loaded.

Does the dev.workers.3labsio.kingofthehill/king-of-the-hill MCP server require authentication?

No. We connected to dev.workers.3labsio.kingofthehill/king-of-the-hill without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the dev.workers.3labsio.kingofthehill/king-of-the-hill MCP server still maintained?

dev.workers.3labsio.kingofthehill/king-of-the-hill is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.