Analytics
semipro.coach
Analyzes cycling-event GPS routes to provide demand intelligence for event planning.
ENDPOINT 1
https://api.semipro.coach/mcp
MCP server metadata
- Name
- semipro-cycling-intelligence
- Version
- 1.0.0
SEMIPRO Cycling Intelligence currently provides bounded cycling-event route analysis. Use analyse_event_route for a GPX course. Do not use it for a completed FIT activity, athlete-specific coaching, training prescriptions, medical conclusions or outcome predictions. Public Activity Intelligence remains evaluation-only and is intentionally not exposed as a callable tool.
Known tools 1
analyse_event_routeAnalyse a cycling-event GPX using SEMIPRO Event Demand Intelligence.
Inferred read-onlyCONNECT 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.semipro-cycling-intelligence]
url = "https://api.semipro.coach/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"semipro-cycling-intelligence": {
"type": "http",
"url": "https://api.semipro.coach/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: semipro-cycling-intelligence
Remote MCP URL: https://api.semipro.coach/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": {
"semipro-cycling-intelligence": {
"url": "https://api.semipro.coach/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"semipro-cycling-intelligence": {
"type": "http",
"url": "https://api.semipro.coach/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "semipro-cycling-intelligence",
"transport": "streamable-http",
"url": "https://api.semipro.coach/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.