Espn Core Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

Sports data from the ESPN core API. No key required.

The publisher's own server: core.blue

VerifiedSTDIODesktop only

Overview

AI-generated overview

An MCP server that gives an assistant access to ESPN core API sports data, with no API key required.

What you can do
It exposes ESPN core API sports data to an assistant, letting it look up sports information through the ESPN service. The registry description states it is sports data from the ESPN core API and that no key is required. No tool list is published, so the exact operations are not documented here.
When to use it
Worth considering when an assistant needs sports data from ESPN during a conversation, for example scores, teams, or related sports lookups. It is a local desktop-only server, so it suits users running an MCP client on their own machine.
Requirements
Runs as a local process on the user's machine, installed from the npm package espn-core-mcp over stdio. Desktop only; no web executable. No authentication, environment variables, or headers are declared. Network access to the ESPN API is implied by the description.
Before you install
No credentials, payments, or write actions are indicated. Because it queries a third-party sports API, requests and any parameters the assistant sends go to ESPN. The published tool list is empty, so review the actual tools after installing before relying on them.

Installation

In SourceWeft

  1. Open Espn Core Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Core integrations