Is Wc26 MCP safe to use?

Wc26 MCP has an HVTrust score of 55.5/100 (Grade C), ranked #766 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Wc26 MCP?

Wc26 MCP scores 55.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 34 GitHub stars and is categorized under MCP Servers.

Wc26 MCP

jordanlyall/wc26-mcp

AI companion for FIFA World Cup 2026 — 18 tools covering matches, teams, venues, city guides, fan zones, visa info, head-to-head records, and more. Works with Claude, ChatGPT, Cursor, and Telegram.

MCP Servers TypeScript Listed MIT

Is Wc26 MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.4 / 10

Provenance None

Signed commits 0%

Last push yesterday

Compare Wc26 MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Wc26 MCP scores 55.5/100 (Grade C), ranked #766 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.4/10; recent commits are unsigned; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Wc26 MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Wc26 MCP’s 55.5.

Where the 55.5 comes from

HVTrust dimensions vs the MCP Servers average

55.5 / 100 · 100.0% confidence

Wc26 MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

4.2 / 25

6.1 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.4 / 17

0.8 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.9 / 20

5.8 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.2 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 170 spots (#930 → #760)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.4/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Wc26 MCP View MCP Servers Report missing data

57.6

Activity sub-score · out of 100

#423

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

452

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #765

Analysis

Activity Inputs

57.6 / 100

StarsRepository reach

9.3 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

18.6 / 25

CommunityFork signal

4.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.4 / 10

OpenSSF Scorecard · scanned Sep 15, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 4

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Wc26 MCP

Wc26 MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Wc26 MCP publish package provenance?

No published build provenance is currently detected for Wc26 MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Wc26 MCP have an OpenSSF Scorecard?

Wc26 MCP has an OpenSSF Scorecard score of 3.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Wc26 MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Wc26 MCP use?

Wc26 MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Wc26 MCP's commits signed?

0% of the last 100 commits to Wc26 MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Wc26 MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintain Wc26 MCP?

For maintainers

HVTrust scores Wc26 MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 170 spots (#930 → #760)

2026-09-23

HVTrust Changed

HVTrust up 29.3pts (26.3 → 55.6)

2026-09-22

Newly Listed

First tracked at rank #930

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Grade Changed

Trust grade D → C

2026-09-11

Rank Moved

Rank rose 457 spots (#1212 → #755)

2026-09-11

HVTrust Changed

HVTrust up 19.2pts (36.1 → 55.3)

2026-09-08

Rank Moved

Rank dropped 14 spots (#1190 → #1204)

2026-09-07

Rank Moved

Rank dropped 16 spots (#1174 → #1190)

2026-09-06

Rank Moved

Rank dropped 13 spots (#1161 → #1174)

2026-09-05

Rank Moved

Rank dropped 33 spots (#1128 → #1161)

2026-09-04

Rank Moved

Rank dropped 19 spots (#1109 → #1128)

2026-09-03

Rank Moved

Rank dropped 50 spots (#1059 → #1109)

2026-09-02

Rank Moved

Rank dropped 44 spots (#1015 → #1059)

2026-09-01

Scorecard Added

OSSF Scorecard: 3.4/10

2026-09-01

Rank Moved

Rank rose 209 spots (#1224 → #1015)

2026-09-01

HVTrust Changed

HVTrust up 15.7pts (20.4 → 36.1)

2026-08-31

Rank Moved

Rank dropped 22 spots (#1202 → #1224)

2026-08-30

Rank Moved

Rank dropped 22 spots (#1180 → #1202)

2026-08-29

Rank Moved

Rank dropped 26 spots (#1154 → #1180)

2026-08-28

Rank Moved

Rank dropped 21 spots (#1133 → #1154)

2026-08-27

Rank Moved

Rank dropped 13 spots (#1120 → #1133)

2026-08-26

Rank Moved

Rank dropped 62 spots (#1058 → #1120)

2026-08-17

Rank Moved

Rank rose 16 spots (#1075 → #1059)

2026-08-16

Rank Moved

Rank dropped 34 spots (#1041 → #1075)

2026-08-12

Rank Moved

Rank rose 17 spots (#1056 → #1039)

2026-08-10

Rank Moved

Rank dropped 57 spots (#996 → #1053)

2026-08-08

Newly Listed

First tracked at rank #986

GitHub → npm: wc26-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/wc26-mcp.svg)](https://hvtracker.net/agents/wc26-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/wc26-mcp"><img src="https://hvtracker.net/badge/wc26-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON