football-docs

io.github.withqwertyPublished by GitHub account withqwertyv0.2.1Updated Oct 24, 2026

Searchable football data provider docs for AI coding agents.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives an AI coding agent searchable documentation for a football data provider.

What you can do
  • Search the bundled football data provider documentation from within an assistant session.
  • Retrieve reference material to help an agent write code against that provider's data.
  • Runs as a local stdio process with no tools or configuration details published in the listing.
When to use it
Useful when you are building something on top of this football data provider and want the assistant to consult its documentation while coding, instead of pasting docs into the chat.
Requirements
A local runtime that can run the npm package football-docs over stdio (Node.js). No authentication, environment variables or headers are declared. Desktop-only; not available as a web-executable server.
Before you install
The listing publishes no tool list, README or instructions, so what the tools actually return cannot be verified before installing. It is a local process on your machine; review the package before running it.

Installation

In SourceWeft

  1. Open football-docs 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.

Tools

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

Version history

1
  1. v0.2.1LatestSep 16, 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.