Skip to main content
Glama
rocnubie

17-0 MCP Server

by rocnubie
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

17-0 MCP Server

17-0 - Build the Perfect NFL Roster

MCP Badge License: MIT Read Only Node MCP

A Model Context Protocol server that exposes the canonical 17-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://17-0.site

🎮 About 17-0

17-0 is a free, fan-made NFL roster strategy game built around a focused question: can seven offensive legends produce a perfect 17-game regular season? Each run gives the player seven random team-and-era combinations. The player chooses one eligible legend from each spin, fills a compact fantasy-style offense, and then lets the simulation grade the roster across a full regular season. The format keeps a complete run short while still forcing decisions about positional balance, player eras, and how much risk to take on each pick.

Related MCP server: 27-0-mcp

Key Features

  • Seven-player offensive roster: Every lineup uses one quarterback, two running backs, two wide receivers, one tight end, and one flex player. The fixed structure makes every spin consequential and prevents a roster from becoming a simple list of famous names.

  • Team-and-era spins: Picks begin with a randomly selected NFL franchise and historical era. Players draft within that constraint instead of searching an unrestricted player database.

  • Seventeen-game simulation: A completed roster is evaluated over the length of the current NFL regular season. The target is an undefeated 17-0 result rather than a playoff bracket.

  • Daily challenge: The daily mode gives players the same theme and deterministic seed, creating a comparable challenge that resets at midnight Eastern Time. Rotating constraints cover divisions, decades, and other roster themes.

  • Leaderboards and share results: Players can compare daily and all-time results. Compact share links and spoiler-free cards communicate roster quality without revealing every drafted player.

  • No account required: Free play and the daily challenge can be opened directly in a browser without registration. The site is designed for short sessions on desktop or mobile.

Use Cases

NFL fans can use free play to test dream offenses assembled from different franchises and eras. A player might prioritize a quarterback early, preserve the flex slot for the strongest remaining skill player, or accept a weaker position because a later spin offers a historically deep team. The daily challenge gives friends a common set of constraints, making results easier to compare than independent random runs. Shared result cards also work as a compact way to challenge a group without exposing the entire solution in advance.

The game can also prompt discussion about roster construction. Because positions are fixed and every selection consumes one of only seven slots, choices expose real trade-offs: peak production versus longevity, positional scarcity versus star power, and balanced lineups versus concentrated strengths. The simulation is an entertainment mechanic rather than a prediction of real NFL outcomes.

Who Is It For

17-0 is for NFL and fantasy-football fans who enjoy historical player debates, roster builders, daily games, and quick competitive challenges. It is especially suited to players who want a complete session in a few minutes instead of managing a season-long fantasy team. The site is unofficial and is not affiliated with or endorsed by the NFL.

Tools

get_game_rules

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

Input: no parameters. Returns: text/markdown.

get_official_links

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

Input: no parameters. Returns: text/markdown.

Resources

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

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

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

Prompts

tell_me_about_17_0

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

plan_a_run_17_0

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

Installation

Install via Smithery

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

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

Install from source

git clone https://github.com/rocnubie/17-0-mcp.git
cd 17-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": {
    "17-0-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/17-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. (17-0)

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.7/5.0
Behavior3/5

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

Discloses it is a read operation returning 'verified' data, but lacks details on permissions, rate limits, or side effects. Adject description adequate for a simple tool without annotations.

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

Conciseness4/5

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

Single sentence with clear action and resource. Parenthetical '(17-0)' adds minor noise but does not detract significantly.

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?

For a no-parameter, read-only tool without output schema, the description sufficiently identifies returned content. No gaps.

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, so schema coverage is 100%. Description does not need to add param info; baseline 4 applicable.

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?

Clearly states it returns verified game rules, roster constraints, and public entry points, differentiating from sibling tool 'get_official_links'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives or any prerequisites. Simply states what it does.

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. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.0
    • First observedget_game_rules
    • First observedget_official_links
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one retrieves game rules, the other retrieves official links. There is no functional overlap.

Naming Consistency5/5

Both tools follow the consistent verb_noun pattern 'get_*', making them predictable and easy to distinguish.

Tool Count4/5

With only 2 tools, the server feels minimal but is still reasonable for a narrowly scoped info-providing server. It does not feel excessively thin for its apparent purpose.

Completeness3/5

The domain (17-0 game/platform) likely encompasses more than just rules and links, such as game state or player actions, but the server seems focused on static reference information, so major gaps may not be critical.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

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

  • 20-0 MCP Server

    rocnubie
    A
    license
    A
    quality
    C
    maintenance
    Read-only MCP server exposing the 20-0 NFL perfect season game knowledge surface, including game modes, roster picks, scenarios, FAQ, and official links to AI clients.
    2
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rocnubie/17-0-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server