FootballBin MCP Server
The FootballBin MCP Server provides AI-powered football match predictions for Premier League and Champions League competitions.
Key capabilities:
Get match predictions using the
get_match_predictionstool with detailed forecasts including half-time scores, full-time scores, next goal scorer, corner counts, and confidence levelsFilter predictions by league (EPL/PL or UCL/CL), matchweek number, home team, and/or away team
Access key player insights with reasoning for each predicted match
View match details including kickoff times, match IDs, and match status
Use flexible team aliases (e.g., "united" for Man Utd, "spurs" for Tottenham, "barca" for Barcelona)
Integrate via multiple methods: npm package, npx execution, remote HTTPS endpoint, or Claude.ai connector
Make direct API calls using JSON-RPC 2.0 protocol for integration with AI agents and MCP clients
Provides AI-powered match predictions for Premier League games, including half-time and full-time scores, next goal scorer, corner counts, and key player insights.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FootballBin MCP Serverget predictions for the next Manchester United match"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FootballBin MCP Server
A Model Context Protocol (MCP) server that provides AI agents with access to football match predictions for the Premier League and Champions League.
Requirements
Node.js 18+ (check with
node --version)
Related MCP server: mcp-sofascore
Installation
Option 1: npm (Recommended)
npm install -g footballbin-mcp-serverOption 2: npx (No Install)
npx footballbin-mcp-serverOption 3: Remote Endpoint
No installation required - use the hosted endpoint directly:
https://ru7m5svay1.execute-api.eu-central-1.amazonaws.com/prod/mcpQuick Start
Claude.ai (Easiest - No Install)
Go to Settings > Connectors
Click Add custom connector
Enter:
https://ru7m5svay1.execute-api.eu-central-1.amazonaws.com/prod/mcp
Claude Desktop
Requires Node.js 18+
Step 1: Install globally
npm install -g footballbin-mcp-serverStep 2: Find your Node.js path (must be v18+)
which node && node --versionStep 3: Add to claude_desktop_config.json:
{
"mcpServers": {
"footballbin": {
"command": "/path/to/node",
"args": ["/path/to/node_modules/footballbin-mcp-server/dist/index.js"]
}
}
}Example configs:
macOS with nvm:
{
"mcpServers": {
"footballbin": {
"command": "/Users/YOU/.nvm/versions/node/v20.x.x/bin/node",
"args": ["/Users/YOU/.nvm/versions/node/v20.x.x/lib/node_modules/footballbin-mcp-server/dist/index.js"]
}
}
}macOS with Homebrew:
{
"mcpServers": {
"footballbin": {
"command": "/opt/homebrew/bin/node",
"args": ["/opt/homebrew/lib/node_modules/footballbin-mcp-server/dist/index.js"]
}
}
}Windows:
{
"mcpServers": {
"footballbin": {
"command": "C:\\Program Files\\nodejs\\node.exe",
"args": ["C:\\Users\\YOU\\AppData\\Roaming\\npm\\node_modules\\footballbin-mcp-server\\dist\\index.js"]
}
}
}Config file location:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Other MCP Clients
Use the remote endpoint:
https://ru7m5svay1.execute-api.eu-central-1.amazonaws.com/prod/mcpFeatures
AI Match Predictions:
Half-time score
Full-time score
Next goal scorer
Corner count predictions
Supported Leagues:
Premier League (EPL)
UEFA Champions League (UCL)
Key Players: Each match includes key player insights with reasoning
Tool: get_match_predictions
Input Parameters
Parameter | Type | Required | Description |
| string | Yes |
|
| number | No | Matchweek number (defaults to current) |
| string | No | Filter by home team (e.g., |
| string | No | Filter by away team (e.g., |
Team Aliases
Alias | Maps To |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example Response
{
"league": "premier_league",
"matchweek": 22,
"count": 10,
"app_link": "https://apps.apple.com/app/footballbin/id6757111871",
"matches": [
{
"match_id": "epl_mw22_liv_bur",
"home_team": "Liverpool",
"away_team": "Burnley",
"kickoff_time": "2026-01-17T15:00:00Z",
"status": "scheduled",
"predictions": [
{ "type": "Half Time Result", "value": "2:0", "confidence": 75 },
{ "type": "Full Time Result", "value": "4:0", "confidence": 75 },
{ "type": "Next Goal", "value": "Home,Wirtz", "confidence": 75 },
{ "type": "Corner Count", "value": "9:3", "confidence": 75 }
],
"key_players": [
{
"player_name": "Florian Wirtz",
"reason": "12 goals, 14 assists. Liverpool's creative hub."
}
]
}
]
}Direct API Usage
List Tools
curl -X POST https://ru7m5svay1.execute-api.eu-central-1.amazonaws.com/prod/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"tools/list","id":1}'Get Predictions
curl -X POST https://ru7m5svay1.execute-api.eu-central-1.amazonaws.com/prod/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "get_match_predictions",
"arguments": {"league": "premier_league"}
},
"id": 1
}'Registry Links
Official MCP Registry: https://registry.modelcontextprotocol.io
FootballBin App
Get the full experience with the FootballBin iOS app:
Features:
Live match tracking
AI player valuations
Detailed match predictions
Player news and discussions
Technical Details
Protocol: JSON-RPC 2.0 / MCP
Transport: stdio (npm) or HTTPS (remote)
Runtime: Node.js 20+
Error Codes
Code | Meaning |
-32700 | Parse error |
-32600 | Invalid request |
-32601 | Method not found |
-32602 | Invalid params |
License
MIT License - see LICENSE file.
Links
Available Tools
1 toolget_match_predictionsC
Get AI-powered predictions for Premier League and Champions League matches including half-time score, full-time score, next goal scorer, and corner predictions.
| Name | Required | Description | Default |
|---|---|---|---|
| league | Yes | League to get predictions for. Accepts: "premier_league", "epl", "pl", "champions_league", "ucl", "cl" | |
| matchweek | No | Matchweek number (optional, defaults to current matchweek) | |
| home_team | No | Filter by home team name (optional, e.g., "chelsea", "arsenal", "man_utd") | |
| away_team | No | Filter by away team name (optional, e.g., "liverpool", "wolves") |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'AI-powered predictions' but lacks details on rate limits, authentication needs, data freshness, confidence levels, or response format. For a tool with no annotations, this leaves critical behavioral traits unspecified.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that efficiently conveys the tool's purpose, scope, and prediction types without any wasted words. It is appropriately sized and front-loaded with essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is incomplete. It does not address behavioral aspects like rate limits or authentication, nor does it explain the return values or prediction format. For a tool with no structured data beyond the input schema, more contextual information is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds no additional parameter semantics beyond what the schema provides, such as explaining interactions between parameters or usage examples. Baseline 3 is appropriate when the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with specific verbs ('Get AI-powered predictions') and resources ('Premier League and Champions League matches'), including the types of predictions (half-time score, full-time score, etc.). It distinguishes itself from hypothetical alternatives by specifying the leagues and prediction types, though there are no actual sibling tools to differentiate from.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual usage. It lists what the tool does but offers no explicit when/when-not instructions or comparisons to other tools, which is a significant gap in usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions.
One tool is too few for a server focused on football match predictions, as it suggests a limited scope that may not cover related operations like historical data, team statistics, or user preferences. This feels thin for the apparent domain.
The server is severely incomplete for football predictions, as it only provides predictions without supporting tools for data retrieval, updates, or other predictive features like odds analysis or match scheduling. This creates significant gaps for agent workflows.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Football fixtures, standings, and odds intelligence for AI agents.
Grounded sports predictions plus European soccer and tennis arbitrage data for AI agents.
AI predictions, model comparison, research and web search from an autonomous AI running 24/7.
NFL analytics tools for AI agents: stats, fantasy, injuries, schedules, and advanced analysis.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides tools to query football match data, odds, standings, and team statistics via natural language, integrating with the football-scraper-api.
- FlicenseNot gradedqualityDmaintenanceProvides live football match data from Sofascore, including formations, injuries, betting odds, and league positions, enabling natural language queries about matches.1
- FlicenseNot gradedqualityDmaintenanceEnables natural language querying of football/soccer data via the API-Football service, providing access to leagues, teams, players, fixtures, standings, and statistics.3
- AlicenseAqualityBmaintenanceProvides AI assistants with live football data for 90+ leagues including tables, results, fixtures, model probabilities, and Monte Carlo season projections from football-charts.com.1066MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/billychl1/footballbin-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server