Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/abaiii168/world-cup-2026-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/abaiii168/world-cup-2026-mcp-server/world-cup-2026)<a href="https://agentmods.dev/mcp/abaiii168/world-cup-2026-mcp-server/world-cup-2026"><img src="https://agentmods.dev/badge/mcp/abaiii168/world-cup-2026-mcp-server/world-cup-2026/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/abaiii168/world-cup-2026-mcp-server/world-cup-2026"><img src="https://agentmods.dev/badge/mcp/abaiii168/world-cup-2026-mcp-server/world-cup-2026.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
world-cup-2026 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"world-cup-2026": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 12 lines scan A db27e4e178fa
world-cup-2026 is an MCP server published in the GitHub repository abaiii168/world-cup-2026-mcp-server (1 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
wc26
FIFA World Cup 2026 data: matches, teams, venues, city guides, fan zones, and more. Runs locally from the wc26-mcp npm package.
footballcharts-mcp
Tables, results, model probabilities and Monte Carlo projections for 90+ football leagues. Runs locally from the footballcharts-mcp npm package. Needs 1 environment variable to run.
playerelo-mcp
MCP server "playerelo-mcp" as configured in mwolters-cmyk/playerelo-mcp. Runs locally from the playerelo-mcp Python package. Needs 2 environment variables to run.
futbol-atlas
The Laws of the Game and world football's major competitions, every claim cited to primary sources. Remote server at futbolatlas.app.
sports-data-mcp-server
MCP-Server für Sportdaten — Live-Scores, Tabellen, Spieler-Statistiken und historische Ergebnisse weltweit. Runs locally from the sports-data-mcp-server Python package.
feyod-mcp
MCP server "feyod-mcp" as configured in jeroenvdmeer/feyod-mcp. Runs locally from the feyod-mcp Python package.