World Cup 2026 Tour
OCI · GHCR.IO/ABAIII168/WORLD-CUP-2026-MCP-SERVER:0.1.1 · SCANNED SEP 20
Free MCP server for World Cup 2026 fixtures, local kickoff times, and Dataset JSON-LD.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 96 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 347 tokens (~69/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the World Cup 2026 Tour MCP server?
World Cup 2026 Tour runs locally as a container image, launched with docker run --rm -i ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1
claude mcp add abaiii168-world-cup-2026 -- docker run --rm -i ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1
{
"mcpServers": {
"abaiii168-world-cup-2026": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1"
]
}
}
} {
"servers": {
"abaiii168-world-cup-2026": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1"
]
}
}
} codex mcp add abaiii168-world-cup-2026 -- docker run --rm -i ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"abaiii168-world-cup-2026": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1"
],
"enabled": true
}
}
} mcp_servers:
abaiii168-world-cup-2026:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1"] {
"McpServers": {
"abaiii168-world-cup-2026": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1"
]
}
}
} {
"mcpServers": {
"abaiii168-world-cup-2026": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_world_cup_2026_dataset Get World Cup 2026 Dataset ~38
Return Dataset JSON-LD metadata and all 104 public fixtures in UTC for citation, indexing, or data-directory use.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_world_cup_2026_match Get One World Cup 2026 Match ~80
Return one World Cup 2026 fixture by match id, including teams, venue, stage, kickoff, app link, share-card link, and calendar link.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | World Cup 2026 Tour public match id. |
| timezone | string | – | IANA time zone for kickoff conversion. Defaults to UTC. |
No output schema declared.
No examples provided.
get_world_cup_2026_matches Get World Cup 2026 Matches ~128
Return World Cup 2026 fixtures in a requested IANA time zone, optionally filtered by stage, group, or team code/name.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Group letter A-L for group-stage filtering. |
| limit | integer | – | Maximum number of matches to return. |
| stage | string | – | – |
| team | string | – | Team code or English team name, for example MEX, BRA, Japan, or United States. |
| timezone | string | – | IANA time zone, for example Europe/London or America/New_York. Defaults to UTC. |
No output schema declared.
No examples provided.
get_world_cup_2026_metadata Get World Cup 2026 API Metadata ~37
Return metadata, attribution, endpoint links, and schema notes for the free World Cup 2026 Tour public API.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_world_cup_2026_next_match Get Next World Cup 2026 Match ~64
Return the nearest upcoming World Cup 2026 fixture from the public schedule API in the requested IANA time zone.
| Name | Type | Req | Description |
|---|---|---|---|
| timezone | string | – | IANA time zone, for example Asia/Tokyo or Europe/London. Defaults to UTC. |
No output schema declared.
No examples provided.
What is the World Cup 2026 Tour MCP server?
World Cup 2026 Tour is an MCP server listed in the public MCP registry as io.github.abaiii168/world-cup-2026. Free MCP server for World Cup 2026 fixtures, local kickoff times, and Dataset JSON-LD. This page covers its container image (ghcr.io/abaiii168/world-cup-2026-mcp-server:0.1.1).
Is the World Cup 2026 Tour MCP server safe to use?
World Cup 2026 Tour scores 52 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the World Cup 2026 Tour MCP server expose?
World Cup 2026 Tour exposes 5 tools: get_world_cup_2026_metadata, get_world_cup_2026_matches, get_world_cup_2026_next_match, get_world_cup_2026_match, get_world_cup_2026_dataset. Their descriptions and schemas cost roughly 347 tokens of context every time the server is loaded.
Is the World Cup 2026 Tour MCP server still maintained?
World Cup 2026 Tour is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the World Cup 2026 Tour MCP server under?
World Cup 2026 Tour declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.