Skip to main content
Glama
Rocniubi

27-0-mcp

by Rocniubi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

27-0 MCP Server

27-0 NRL Game - Build the Perfect XIII, Go Undefeated

MCP Badge License: MIT Stdio Transport Zero Config MCP Read Only

A Model Context Protocol server that exposes the canonical 27-0 knowledge surface — game rules, roster constraints, and entry points, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.

Official website: https://27-0game.com

🎮 About 27-0

27-0 is a free browser game for NRL fans who want to build an all-time rugby league XIII and see whether it can survive a perfect season. The site turns an ordinary greatest-player debate into a constrained draft: each round spins an NRL club and era, then the player chooses one eligible legend for the open position. After thirteen picks, the lineup is run through a seeded 27-round season simulation. The goal is an undefeated 27-0 record and the highest available grade, not a prediction of a real NRL result.

Related MCP server: 17-0 MCP Server

Key Features

  • Fixed 13-player lineup — The roster follows the NRL jersey structure: fullback, two wings, two centres, five-eighth, halfback, two props, hooker, two second-rowers, and lock. A pick must fit the position currently open, so famous names alone cannot solve the draft.

  • Club-and-era spins — Every selection starts from a historical club and era pool. Players choose from the legends eligible for that spin instead of searching an unrestricted database.

  • 27-round simulation — A completed XIII is evaluated across 27 rounds, with regular-season and finals stages leading to a grand final. The simulation is deterministic for a given seed and roster, which makes shared runs reproducible.

  • Three draft experiences — Classic keeps player stats visible for number-based decisions. Daily uses the same thirteen spins for everyone, allows one attempt, and resets at midnight AEST. Footy IQ hides the stats so the draft relies on memory and rugby knowledge.

  • Leaderboards and share codes — Players can submit a result to the leaderboard and share a compact code that recreates the run. Leaderboard entries are user-submitted game results, not certified competitive records. The public pages include the play screen, daily challenge, leaderboard, and share routes.

  • Free and independent — The game runs in a browser without an account requirement for play. It is an independent fan project and is not affiliated with the NRL or any club. Player names, statistics, and ratings are site-curated game data used for commentary and parody, not official NRL records.

Use Cases

NRL fans can use Classic to compare the game's displayed player profiles, use Footy IQ to test historical knowledge, or return to Daily for a shared challenge. A group can play the same daily seed, post the resulting record, and open a share link to inspect the lineup and round-by-round story. The fixed positions create meaningful trade-offs between backs, forwards, spine roles, and the strength of each club-era pool.

Who Is It For

27-0 is for rugby league supporters who enjoy all-time debates, roster builders, daily games, and short competitive sessions. It is designed to be completed in a few minutes on desktop or mobile. The simulation is an entertainment mechanic: it should not be read as an official ranking of players, clubs, or likely real-world match outcomes.

Tools

get_game_rules

Return the verified game rules, roster constraints, and public entry points the site exposes. (27-0)

Input: no parameters. Returns: text/markdown.

get_official_links

Return the canonical list of official links for 27-0 (website, support, docs when available).

Input: no parameters. Returns: text/markdown.

Resources

  • site://27-0/rules — Verified game rules, roster-building constraints, and public entry points.

  • site://27-0/faq — Short FAQ generated from public site metadata.

  • site://27-0/links — Canonical URLs to share with users.

Prompts

tell_me_about_27_0

Summarize what the site is, who it's for, and how it works. — 27-0

plan_a_run_27_0

Plan a single play-through using verified rules and entry points. — 27-0

Installation

Install via Smithery

npx -y @smithery/cli install 27-0-mcp --client claude

(Replace claude with cursor, windsurf, or continue for those clients.)

Install from source

git clone https://github.com/Rocniubi/27-0-mcp.git
cd 27-0-mcp
pnpm install

Then add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):

{
  "mcpServers": {
    "27-0-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/27-0-mcp/src/index.mjs"
      ]
    }
  }
}

Debug with MCP Inspector

npx @modelcontextprotocol/inspector node src/index.mjs

Official Links

Development

pnpm install
pnpm start                 # run the server over stdio

License

MIT

Available Tools

2 tools
get_game_rulesA

Return the verified game rules, roster constraints, and public entry points the site exposes. (27-0)

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It states the return content but lacks details on potential caching, freshness, or side effects. However, since it is a simple read operation with no parameters, the basic transparency is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single concise sentence with no wasted words. Front-loaded with purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and simple nature, description adequately covers what is returned. Could mention size limits or pagination, but not necessary for this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist; schema coverage is 100% (empty). Description need not add parameter info. Baseline 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verb 'Return' and explicitly names resources: 'verified game rules, roster constraints, and public entry points'. Distinguishes from sibling 'get_official_links' by focusing on rules and constraints rather than links.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs. alternatives. Context suggests it is for rules/constraints, but no when-not or alternative naming.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv0.1.0
    • First observedget_game_rules
    • First observedget_official_links
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have distinctly different purposes: one returns game rules, the other returns official links. There is no overlap in functionality.

Naming Consistency5/5

Both tools follow a consistent 'get_' prefix followed by a noun describing the resource. The naming pattern is uniform.

Tool Count3/5

With only two tools, the server feels minimal. While the tools are appropriate for a simple information retrieval server, the number is at the low end of the acceptable range for a game-related MCP.

Completeness2/5

The server only provides static information retrieval. For a game MCP, one would expect additional tools for player interaction, game state management, or rule lookup by topic. The lack of such features creates significant gaps.

Resources

Related MCP Connectors

Related MCP Servers

  • 17-0 MCP Server

    Rocniubi
    A
    license
    A
    quality
    C
    maintenance
    Exposes the canonical 17-0 knowledge surface including game rules, roster constraints, and entry points for the NFL roster strategy game to MCP-compatible AI clients.
    2
    MIT

  • 17-0 MCP Server

    rocnubie
    A
    license
    A
    quality
    C
    maintenance
    Provides verified game rules, official links, and FAQ for the 17-0 NFL roster strategy game to MCP-compatible AI clients.
    2
    MIT

  • 27-0 MCP Server

    rocnubie
    A
    license
    A
    quality
    C
    maintenance
    Provides game rules, roster constraints, FAQ, and official links for the 27-0 NRL fantasy draft game, enabling AI clients to retrieve this knowledge.
    2
    MIT