7-0 MCP Server
7-0 MCP Server
7-0 - 2026 World Cup Squad Builder and Knockout Simulator
🌐 English · 简体中文 · Português (BR) · Español · Français · Deutsch
A Model Context Protocol server that exposes the canonical 7-0 knowledge surface — game modes, roster picks, and scenarios, 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://seteazero.com
🎮 About 7-0
7-0 is a free, no-signup browser game where the player builds a squad for the 2026 World Cup, advances through seven knockout rounds, and tries to lift the trophy without dropping a match. The squad is drafted from real 2026 World Cup rosters scraped from public Wikipedia squad pages, and matches are decided by a deterministic event-based simulation engine that runs entirely client-side. There is no waiting for servers, no account to register, and no in-app purchases — the page loads, the squad is built, and the tournament plays out in the browser. Permalinks are stored in Cloudflare D1 so any run can be shared and reproduced exactly, with the same seven matches and the same scoreline-by-minute story for everyone who opens the URL.
Related MCP server: 27-0-mcp
Key Features
2026 World Cup squads — every national team's roster is pulled from public Wikipedia squad pages, so the player list reflects actual qualified players rather than historical generics.
Seven-round knockout structure — group stage through the final is collapsed into a single seven-win path, so the run is short enough to play in one sitting but long enough to make every selection matter.
Deterministic event-based simulation — the match engine emits a chronological sequence of in-game events (chances, fouls, cards, goals) that the same input always reproduces, which is what makes shared permalinks replay identically.
Historical World Cup database — past tournament data is sourced from the Fjelstul World Cup Database (CC-BY-SA 4.0), giving stat tooltips and historical context that line up with the public record.
Five-language interface — English, Spanish, French, German, and Brazilian Portuguese ship at launch; each language is served from its own locale-prefixed route.
Cloudflare Pages + D1 permalinks — finished runs save into D1 and reopen at a content-addressable URL, so a friend opening the link sees the same squad, the same seven matches, and the same trophy lift (or elimination).
No FIFA affiliation, no logos — team and player names appear as factual references; no crests, sponsor marks, or photographs are used, keeping the surface IP-light and family-friendly.
Use Cases
Friend-group bracket competition — everyone runs the same seeded tournament and compares squad choices through the shared permalink.
Match-day warm-up — play a quick seven-round run before a real fixture as a low-stakes way to read into form and tactics.
Group-stage and knockout speculation — test how different squad compositions hold up against the same simulated opponents to argue for one starting eleven over another.
Localized fan communities — Spanish, Portuguese, French, German, and English speakers can all share the same run URL and read the result in their own language.
Streaming and short-form content — record a deterministic run and post the link so viewers can replicate the bracket and react alongside.
Who Is It For
7-0 is for football fans who follow the 2026 World Cup and want a quick, structured way to test predictions about squad strength without setting up a fantasy league. It fits casual users who play one or two runs over a tournament cycle, as well as more invested fans who run many configurations against the same simulator to argue for a specific tactical or selection point. The game also works for friend groups that want a shared, reproducible bracket without registering accounts, and for content creators who need a deterministic source of "what if" tournament outcomes. Anyone who would otherwise sketch brackets on paper has a faster, shareable equivalent here.
Tools
list_scenarios
Return the canonical list of game modes and scenarios the site exposes (free play, daily, leaderboards, etc.). (7-0)
Input: no parameters. Returns: text/markdown.
get_official_links
Return the canonical list of official links for 7-0 (website, support, docs when available).
Input: no parameters. Returns: text/markdown.
Resources
site://7-0/scenarios— Available game modes, scenarios, and roster-building constraints.site://7-0/faq— Short FAQ generated from public site metadata.site://7-0/links— Canonical URLs to share with users.
Prompts
tell_me_about_7_0
Summarize what the site is, who it's for, and how it works. — 7-0
plan_a_run_7_0
Plan a single play-through: pick a mode, draft a roster strategy, and predict outcomes. — 7-0
Installation
Install via Smithery
npx -y @smithery/cli install 7-0-mcp --client claude(Replace claude with cursor, windsurf, or continue for those clients.)
Install from source
git clone https://github.com/rocnubie/7-0-mcp.git
cd 7-0-mcp
pnpm installThen add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):
{
"mcpServers": {
"7-0-mcp": {
"command": "node",
"args": [
"/absolute/path/to/7-0-mcp/src/index.mjs"
]
}
}
}Debug with MCP Inspector
npx @modelcontextprotocol/inspector node src/index.mjsOfficial Links
Website: https://seteazero.com
Support: support@seteazero.com
Development
pnpm install
pnpm start # run the server over stdioLicense
MIT
Available Tools
2 toolsget_official_linksA
Return the canonical list of official links for 7-0 (website, support, docs when available).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries full burden. It discloses the return type ('canonical list') and contents (website, support, docs when available). However, it does not address potential behaviors like data freshness, empty results, or side effects. Adequate but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence of 16 words, front-loaded with the action verb 'Return'. No redundancy, every word adds value. Ideal conciseness for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters, no output schema, and a straightforward purpose, the description is largely complete. It specifies what is returned. Minor gap: lacks mention of output format (e.g., list of URLs). Still sufficient for agent selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters in schema, so schema coverage is 100%. Description adds no parameter info, but with zero parameters, the baseline is 4. No need for further elaboration.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Return', the resource 'official links', and specifies the scope 'for 7-0' with examples like website, support, docs. It distinguishes from sibling tool 'list_scenarios' by focusing on links vs scenarios.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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. The sibling tool 'list_scenarios' is known but no differentiation or exclusions provided. The description is purely functional with no usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_scenariosA
Return the canonical list of game modes and scenarios the site exposes (free play, daily, leaderboards, etc.). (7-0)
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Only states it returns a list, with no mention of side effects, caching, or read-only nature. Minimal behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, compact, and informative. The parenthetical '(7-0)' is minor and doesn't disrupt clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple, zero-parameter tool. Describes what the list contains, though lacks return format details. Suitable for tool selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters (baseline 4). Description adds value by listing examples of content ('free play, daily, leaderboards'), enhancing understanding beyond empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'Return' and the resource 'canonical list of game modes and scenarios', with examples. Distinguishes from sibling 'get_official_links' which likely has different purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or alternatives guidance. Usage is implied by the tool's clear purpose, but lacks exclusions or comparison with sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
The two tools address entirely different concerns: one lists game scenarios, the other returns official links. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern with underscores: list_scenarios and get_official_links.
With only 2 tools, the server feels minimal. While it may serve a narrow purpose, most domains expect at least a handful of tools for interactive tasks.
The tools only provide static lists. Missing core actions like selecting a scenario, submitting scores, or user interactions make the surface incomplete for the implied game domain.
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
Read-only, deterministic AI triage and readiness tools implementing Sophon's published rubrics.
Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.
Read-only game, setup, place, evidence and travel decision tools with explicit provenance.
Pre-computed market data that improves agent reasoning, reduces token usage, and replaces pipelines.
Related MCP Servers
- AlicenseAqualityCmaintenanceExposes 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.2MIT
- AlicenseAqualityCmaintenanceProvides read-only access to the 27-0 NRL game knowledge including rules, roster constraints, and official links for MCP-compatible AI clients.2MIT
- AlicenseAqualityCmaintenanceProvides verified game rules, official links, and FAQ for the 17-0 NFL roster strategy game to MCP-compatible AI clients.2MIT
- AlicenseAqualityCmaintenanceProvides game rules, roster constraints, FAQ, and official links for the 27-0 NRL fantasy draft game, enabling AI clients to retrieve this knowledge.2MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/7-0-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server