Sports Context Protocol MCP server
io.github.Dswane/sports-context-protocol·v0.1.2Self-learning operational context layer for AI sports agents. Profile 001: golf.
0 stars52 downloads/wk
Reviews
Write oneNobody has reviewed Sports Context Protocol yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Sports Context Protocol tools (9, 3 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
check_booking_actionChecks whether a booking is allowed, blocked, risky, or warns based
check_pricing_actionChecks whether a quoted or discounted price is allowed, given the
create_soft_holdwrite actionCreates a temporary hold on a tee time before confirmation. Marks
explain_actionExplains a decision result for a chosen audience: golfer (simple, no
get_available_inventoryFinds available tee times near a preferred time. Never returns
get_course_contextReturns the full operating context for the course: tee-sheet summary,
get_learning_insightsReturns what SCP has learned: lessons, operator preferences, pricing
submit_outcome_feedbackwrite actionThe learning tool. Attaches an outcome to a past decision and
write_decision_eventwrite actionLogs a decision event to the ledger. Most decision tools write their
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan52 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 128 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Sports Context Protocol compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,255 servers
- Tools
- 9
- the typical server has 7
- Tools that change things
- 33%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 52
- more than 43% of 12,191 servers with a package
What its tools let an agent do: 6 read · 2 create · 1 change
Install Sports Context Protocol in Claude Code, Cursor or VS Code
Runs npx -y sports-context-protocol on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add sports-context-protocol -- npx -y sports-context-protocol
What the publisher says
From the Sports Context Protocol repository's README, as published. We do not edit it. Read it on GitHub
SCP Golf — Profile 001 of the Sports Context Protocol
The context, safety, and memory layer for sports agents. Golf first.
Before a sports agent acts, it checks SCP. Then SCP learns from what happened.
SCP — Sports Context Protocol — is an open context layer for AI agents operating in sports. Every sport venue has the same five things underneath: inventory, rules, actions, consequences, and memory. SCP is the standard way an agent reads those before it acts, and learns from the outcome after.
SCP Golf is Profile 001 — the first working profile. Golf is the cleanest wedge because an agent cannot safely book, price, move, or recommend anything at a course without understanding tee-sheet state, protected inventory, pricing policy, pace risk, events, and operator memory. Golf makes the problem impossible to ignore.
This repository is SCP Golf Alpha: a synthetic demo course, a local MCP server, booking and pricing safety checks, soft holds, a decision ledger, and a self-learning memory. No real course data, no integrations, no database.
- Protocol-level spec: docs/SCPCORESPEC.md
- The profile system: docs/SCP_PROFILES.md
- This profile: docs/SCPGOLFPROFILE.md
Why golf agents need this
AI golf agents are coming — answering calls, booking tee times, quoting prices, moving reservations. The problem: most agents only know the conversation. They do not know the course: the tee-sheet state, the member protections, the league blocks, the pricing floor, the pace risk, the operator's preferences, and what happened the last time a similar decision was made.
SCP Golf gives them that, and then it learns.
What the alpha does
June 6, 2026: a 67-slot tee sheet with member, league, and outing blocks.
- Models one synthetic course — Harbor Ridge Golf Club — for Saturday,
logging, outcome feedback, and learning insights.
- Exposes the course as 11 MCP resources (read-only context).
- Exposes 9 MCP tools for safe booking, pricing, soft holds, decision
overrides, pace issues, price rejections — so the next similar decision is better.
- Exposes 4 MCP prompts (reusable workflows).
- Logs every decision to a ledger and learns from outcomes — operator
Install
npm install
npm run build
npm run typecheck
npm run testRun
npm run dev # runs the MCP server on stdio (tsx, no build needed)
npm start # runs the compiled server from dist/Test it interactively with the MCP Inspector:
npx @modelcontextprotocol/inspector npm run devThe tools
The resources
scp://course/demo and its children: context, tee-sheet, booking-policy, pricing-policy, events, weather, pace, decision-ledger, learning-memory, soft-holds.
The self-learning loop
This is the heart of SCP. It is operational learning — no model training.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Sports Context Protocol: common questions
- Is Sports Context Protocol MCP server safe?
- Mostly: it is graded B (82/100). Read the Sports Context Protocol safety report
- How do I install Sports Context Protocol?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Sports Context Protocol need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Sports Context Protocol maintained?
- The last commit was 166 days ago (2026-05-22). The latest release is v0.1.2.
- How does Sports Context Protocol compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,255 servers); tools 9 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.