General Tools
jobsinsportstech.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://jobsinsportstech.com/mcp
MCP server metadata
- Name
- jobs-in-sports-tech
- Version
- 1.2.0
Live listings of open roles at sports technology companies, refreshed daily from employers' own job feeds by jobsinsportstech.com.
Known tools 3
search_jobsSearch open roles at sports technology companies (sports data, betting tech, wearables, fan engagement, ticketing, performance analytics, fitness tech, clubs and leagues).
Inferred read-onlylist_hiring_companiesList sports technology companies ranked by how many open roles they have, with how many roles each added in the last 30 days.
Inferred read-onlysubscribe_to_job_alertsSign an email address up for Jobs in Sports Tech job alert emails, optionally with preferred regions and job functions.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.jobs-in-sports-tech]
url = "https://jobsinsportstech.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"jobs-in-sports-tech": {
"type": "http",
"url": "https://jobsinsportstech.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: jobs-in-sports-tech
Remote MCP URL: https://jobsinsportstech.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"jobs-in-sports-tech": {
"url": "https://jobsinsportstech.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"jobs-in-sports-tech": {
"type": "http",
"url": "https://jobsinsportstech.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "jobs-in-sports-tech",
"transport": "streamable-http",
"url": "https://jobsinsportstech.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.