MCP/Risk

Directory / server

mikechao/balldontlie-mcp

registry.modelcontextprotocol.io, scanned 2026-08-21, tool surface via package-source

This directory entry reports an automated security scan of mikechao/balldontlie-mcp, scanned 2026-08-21. Trust grade B rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

Automated checks

StatusCheckPolicyResult
WARN Listed on the official MCP registry §1.1

Not found on the official MCP registry. Not disqualifying, but listed servers carry namespace-verified provenance.

PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository
  • Last push: 143 days ago
  • Stars: 26
  • License: MIT
  • Security policy (SECURITY.md): absent
WARN Published package is consistent and attested §1.3
Minor integrity gaps: no npm provenance attestation. 6 findings
  • Package: balldontlie-mcp@0.6.5
  • Ecosystem: npm
  • Age: 499 days
  • Weekly downloads: 61
  • Repo field matches source repo: true
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned; no high-risk capability signals. 1 finding
  • Detected capabilities: none
INFO Transport & authentication §3

Local (stdio) server: runs with host-process privileges by design. Transport checks apply to remote servers; scrutiny shifts to §1/§2.

PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for balldontlie-mcp @0.6.5 (npm).

UNVERIFIABLE Server-supplied instructions free of poisoning indicators §5.1–§5.4

No server-supplied instructions or tool descriptions were obtainable to scan.

What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.