Bellator Schedule Intelligence

io.github.Bellator-Schedule-IntelligencePublished by GitHub account Bellator-Schedule-Intelligencev0.4.2Updated Nov 5, 2026

Schedule health, logic audit, and validation.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP endpoint for Bellator Schedule Intelligence that lets an assistant check schedule health, audit scheduling logic, and run validation.

What you can do
  • Check schedule health through the hosted BellatorSI service
  • Audit scheduling logic for problems
  • Run validation on schedules
  • No individual tools are listed, so exact operations are not documented in the supplied material.
When to use it
Useful when an assistant needs to review project or resource schedules and flag health, logic or validation issues, rather than build or edit schedules itself.
Requirements
Remote streamable HTTP endpoint at api.bellatorsi.com; no local package or runtime. Requires a BellatorSI API key sent in the x-api-key header. The agent mint is described as free and includes health and analysis.
Before you install
The API key is a secret sent in the x-api-key header; keep it out of shared logs and prompts. Schedule data is sent to a third-party hosted service. Paid tiers beyond the free agent mint are implied but not detailed.

Installation

In SourceWeft

  1. Open Bellator Schedule Intelligence in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Bellator-Schedule-Intelligence%2Fschedule-intelligence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bellator-schedule-intelligence": {
      "type": "http",
      "url": "https://api.bellatorsi.com/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

3
  1. v0.4.2LatestNov 5, 2026
  2. v0.4.1Nov 4, 2026
  3. v0.4.0Oct 14, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.