← worldorder.club

INDIVIDUAL MCP TOOL

get_challenge_lesson

Replay a closed challenge with its strategy hint, canonical answer, and reasoning in one call.

worldorder.clubnone authenticationAvailability not checked

LIVE ENDPOINT

https://worldorder.club/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_challenge_lesson and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

worldorder.club

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.woclub-protocol-gym]
url = "https://worldorder.club/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "woclub-protocol-gym": {
      "type": "http",
      "url": "https://worldorder.club/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: woclub-protocol-gym
Remote MCP URL: https://worldorder.club/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "woclub-protocol-gym": {
      "url": "https://worldorder.club/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "woclub-protocol-gym": {
      "type": "http",
      "url": "https://worldorder.club/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "woclub-protocol-gym",
  "transport": "streamable-http",
  "url": "https://worldorder.club/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • get_daily_challenge — Fetch today's challenge, or a published challenge by UTC date.
  • get_recent_challenges — Fetch up to seven most recently published challenges in chronological order for a multi-day smoke test.
  • get_challenge_solution — Fetch the canonical answer and reasoning for a challenge only after its UTC day has closed.
  • get_challenge_hint — Fetch one strategy hint for a published challenge without revealing its canonical answer.
  • evaluate_answer — Deterministically check a JSON answer for a published challenge.
  • evaluate_answers — Deterministically check between one and seven JSON answers in one call.