Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sports Context Protocol

NPM · SPORTS-CONTEXT-PROTOCOL · SCANNED SEP 23

Self-learning operational context layer for AI sports agents. Profile 001: golf.

0 this week 82 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 859 tokens (~42/item across 20 items; 9 tools + 11 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Sports Context Protocol MCP server?

Sports Context Protocol runs locally as an npm package, launched with npx -y sports-context-protocol. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · sports-context-protocol

# add to Claude Code
claude mcp add dswane-sports-context-protocol -- npx -y sports-context-protocol
// .cursor/mcp.json
{
  "mcpServers": {
    "dswane-sports-context-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "sports-context-protocol"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dswane-sports-context-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "sports-context-protocol"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dswane-sports-context-protocol -- npx -y sports-context-protocol
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dswane-sports-context-protocol": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "sports-context-protocol"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dswane-sports-context-protocol --command npx --arg -y --arg sports-context-protocol
# ~/.hermes/config.yaml
mcp_servers:
  dswane-sports-context-protocol:
    command: "npx"
    args: ["-y", "sports-context-protocol"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dswane-sports-context-protocol": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "sports-context-protocol"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dswane-sports-context-protocol -t stdio -c npx -a -y sports-context-protocol
// mcp.json
{
  "mcpServers": {
    "dswane-sports-context-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "sports-context-protocol"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Sept 26 0
    • Stability: 0.97 → pass security
  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Sept 2026 · Analysed npm/sports-context-protocol@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~711 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_booking_action ~91

Checks whether a booking is allowed, blocked, risky, or warns based on policy and learned memory. Writes a decision event to the ledger.

NameTypeReqDescription
agentIdstring
courseIdstring
datestring
nowstring
playersinteger
publicAgentboolean
requestedStartTimestringyes

No output schema declared.

No examples provided.

check_pricing_action ~92

Checks whether a quoted or discounted price is allowed, given the absolute floor, time-window rate, discount limits, approval rules, and learned pricing patterns. Writes a decision event.

NameTypeReqDescription
agentIdstring
courseIdstring
currentPricenumberyes
datestring
proposedPricenumberyes
startTimestringyes

No output schema declared.

No examples provided.

create_soft_hold ~86

Creates a temporary hold on a tee time before confirmation. Marks the slot as soft_hold on the tee sheet.

NameTypeReqDescription
agentIdstring
courseIdstring
datestring
golferNamestring
playersinteger
startTimestring
teeTimeIdstring

No output schema declared.

No examples provided.

explain_action ~60

Explains a decision result for a chosen audience: golfer (simple, no internal language), operator (operational detail), or developer (structured detail).

NameTypeReqDescription
actionTypestringyes
audiencestring
resultobjectyes

No output schema declared.

No examples provided.

get_available_inventory ~70

Finds available tee times near a preferred time. Never returns protected, booked, or blocked inventory as bookable.

NameTypeReqDescription
datestring
playersinteger
preferredTimestring
publicAgentboolean
timeWindowMinutesnumber

No output schema declared.

No examples provided.

get_course_context ~66

Returns the full operating context for the course: tee-sheet summary, inventory, booking and pricing policies, events, weather, pace risks, recent decisions, and learning insights. An agent should call this before acting.

NameTypeReqDescription
courseIdstring
datestring

No output schema declared.

No examples provided.

get_learning_insights ~56

Returns what SCP has learned: lessons, operator preferences, pricing and pace patterns, and similar past decisions. Optionally filtered to a decision fingerprint key.

NameTypeReqDescription
courseIdstring
fingerprintKeystring

No output schema declared.

No examples provided.

submit_outcome_feedback ~65

The learning tool. Attaches an outcome to a past decision and updates SCP's learning memory so future similar decisions improve.

NameTypeReqDescription
decisionEventIdstringyes
feedbackTypestringyes
metricsobject
notesstring

No output schema declared.

No examples provided.

write_decision_event ~125

Logs a decision event to the ledger. Most decision tools write their own events; this tool is for agents that want to log an action directly.

NameTypeReqDescription
actionTypestringyes
agentIdstring
allowedbooleanyes
courseIdstring
fingerprintKeystring
inputSummarystringyes
reasonsarray
requiresApprovalboolean
resultSummarystringyes
riskLevelstring
toolNamestringyes

No output schema declared.

No examples provided.

Common questions

What is the Sports Context Protocol MCP server?

Sports Context Protocol is an MCP server listed in the public MCP registry as io.github.Dswane/sports-context-protocol. Self-learning operational context layer for AI sports agents. Profile 001: golf. This page covers its npm package (sports-context-protocol).

Is the Sports Context Protocol MCP server safe to use?

Sports Context Protocol scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Sports Context Protocol MCP server expose?

Sports Context Protocol exposes 9 tools: get_course_context, get_available_inventory, check_booking_action, check_pricing_action, create_soft_hold, and 4 more. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.

Is the Sports Context Protocol MCP server still maintained?

Sports Context Protocol is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Sports Context Protocol MCP server under?

Sports Context Protocol declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.