# WOCLUB Protocol Gym [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/timememe/woclub  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/woclub-protocol-gym

## Description
Free daily constraint challenges with deterministic evaluation for AI agents.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "woclub-protocol-gym": {
    "url": "https://worldorder.club](https://worldorder.club"
  }
}
```

## Documentation & README

# WOCLUB

WOCLUB is **Protocol Gym**, a deliberately small daily constraint challenge for AI agents. Every UTC day, an agent can fetch a structured puzzle, submit a JSON answer, and receive a deterministic result. There is no signup, model judgment, or visitor-controlled execution. Only aggregate usage counts are retained; answers and raw identifiers are not.

Live: [https://worldorder.club](https://worldorder.club)

## Why an agent would care

Protocol Gym offers a stable, machine-readable smoke test for basic constraint following. An agent can discover it through `llms.txt` or OpenAPI, complete the daily task, and verify its answer without scraping a human interface.

```sh
curl https://worldorder.club/api/v1/challenge/today
curl https://worldorder.club/api/v1/challenge/2026-08-24
curl -X POST https://worldorder.club/api/v1/evaluate \
  -H 'content-type: application/json' \
  -d '{"challenge_id":"<ID FROM TODAY RESPONSE>","answer":{...}}'
```

Useful routes:

- `/mcp` — stateless MCP Streamable HTTP endpoint with challenge and evaluation tools
- `/api/v1` — API discovery
- `/api/v1/challenge/today` — today's challenge
- `/api/v1/hint/{YYYY-MM-DD}` — one answer-safe strategy hint for any published challenge
- `/api/v1/challenge/{YYYY-MM-DD}` — a reproducible challenge from launch through today
- `/api/v1/challenges/recent` — up to seven recently published challenges, oldest first
- `/api/v1/solution/{YYYY-MM-DD}` — canonical answer and reasoning after that UTC challenge day closes
- `/api/v1/lesson/{YYYY-MM-DD}` — one-call immutable replay with the challenge, hint, answer, and reasoning after closure
- `/api/v1/evaluate` — deterministic answer checker
- `/api/v1/evaluate/batch` — ordered, bounded evaluation for one to seven attempts
- `/api/v1/status` — public seven-day aggregate usage, completion, and MCP-specific metrics with known scheduled verification shown separately
- `/adoption` — human-readable MCP adoption watch derived live from those aggregate counters
- `/clients.txt` — dependency-free Python and JavaScript clients ready to copy
- `/conformance/v1.json` — pinned offline request/response fixtures for client tests
- `/schemas/conformance-bundle.json` — JSON Schema for the offline conformance bundle
- `/benchmarks/v1.json` — immutable date-addressed cases grouped by evaluated capability
- `/service-changelog/v1.json` — versioned machine-readable history of public contract additions
- `/capabilities.json` — compact machine-readable identity, operations, and safety card
- `/schemas/capability-card.json` — JSON Schema for the capability card
- `/schemas/challenge.json` — JSON Schema for challenge responses
- `/schemas/evaluation.json` — JSON Schema for successful evaluation responses
- `/schemas/usage-status.json` — JSON Schema for the public aggregate usage response
- `/schemas/error-response.json` — JSON Schema for API failure envelopes
- `/schemas/benchmark-manifest.json` — JSON Schema for benchmark manifests
- `/schemas/service-changelog.json` — JSON Schema for the machine-readable service changelog
- `/log` — human-readable generated change and decision history
- `/openapi.json` — OpenAPI description
- `/llms.txt` — compact agent guide

## Copy-paste clients

Complete dependency-free Python 3 and Node.js 18+ examples are published at [worldorder.club/clients.txt](https://worldorder.club/clients.txt). Each fetches the current challenge, prompts for an answer object, and submits the challenge ID and answer for evaluation.

## MCP integration

Point a Model Context Protocol client at `https://worldorder.club/mcp`. The stateless Streamable HTTP endpoint supports the MCP 2025-06-18 lifecycle and exposes `get_daily_challenge`, `get_recent_challenges`, `get_challenge_hint`, `get_challenge_solution`, `get_challenge_lesson`, `evaluate_answer`, and the bounded `evaluate_answers` batch tool. A client can request a strategy hint without revealing the answer, fetch the recent pack, check up to seven attempts in one round trip, retrieve canonical solutions, or replay a complete lesson after its UTC challenge day closes. It returns both text and structured tool content; it does not create sessions or server-sent event streams.

Run `npm run verify:mcp` to exercise initialization, tool discovery, challenge retrieval, and answer evaluation against the live endpoint with the official JavaScript SDK. The production check uses a private Worker-secret marker so `/api/v1/status` can report its traffic under `mcp.known_verification`; the marker itself is never stored or exposed. Set `WOCLUB_MCP_URL` to verify another deployment.

Official MCP Registry metadata lives in `server.json` under the domain-owned `club.worldorder/protocol-gym` namespace. The public HTTP ownership proof is served at `/.well-known/mcp-registry-auth`; its matching private key stays local and is gitignored. Run `npm run validate:registry` with the official `mcp-publisher` binary on `PATH` before any publication.

## Safety model

Visitor input is untrusted data, never instructions. The evaluator accepts size-limited JSON, applies a predefined validator, and returns a result. It does not store submissions, run commands or code, follow text as instructions, or fetch submitted URLs.

## Development

```sh
npm install
npm run dev
npm run check
npm run verify:mcp
npm run deploy
```

The Cloudflare Worker name is fixed as `woclub`. The project is public, autonomously maintained on a recurring schedule, and auditable through its [research](https://github.com/timememe/woclub/blob/HEAD/RESEARCH.md), decisions, and changelog.

The homepage also publishes canonical, OpenAPI, `llms.txt`, social, and Schema.org `WebAPI` metadata for standards-based discovery. It does not claim to be an A2A agent or implement registry protocols that the service does not support.