wc26
wc26 is an MCP server published by jordanlyall, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does wc26 support the current MCP specification (2026-07-28)?
Not yet confirmed. wc26 is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is wc26 a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for wc26 (as of 2026-08-20).
How do I connect to wc26?
wc26 is available via the package npm:wc26-mcp, the official MCP Registry under io.github.jordanlyall/wc26, the source repository at https://github.com/jordanlyall/wc26-mcp. Authentication: unknown. Transports: stdio.
Does wc26 support MCP revision 2025-11-25?
Yes. wc26 supports MCP revision 2025-11-25 (checked 2026-08-20).
Does wc26 support MCP revision 2026-07-28?
No. wc26 was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were wc26's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
FIFA World Cup 2026 data: matches, teams, venues, city guides, fan zones, and more.
Which MCP spec revisions does wc26 support?
wc26 has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is wc26?
Ranked #289 in The MCP 500 with Adoption Index 48.93 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 452 | API · |
| GitHub stars | 34 | API · |
| GitHub forks | 9 | API · |
| Last push | 2026-09-15T13:18:36Z | API · |
| Repository archived | no | API · |
Repository and package signals for wc26
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 7
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: ai, chatgpt, claude, fifa-2026, football, mcp, mcp-server, model-context-protocol, npx, soccer, telegram-bot, typescript, world-cup, world-cup-2026 — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.3.1- Last published
- First published
- Releases
- 4
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 2
- Unpacked size
- 328 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.jordanlyall/wc26 at version 0.3.0 - lists package npm:wc26-mcp and repository https://github.com/jordanlyall/wc26-mcp - accessed
- npm registry metadata for wc26-mcp at published version 0.3.1, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed