General Tools
champfy.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://www.champfy.com/api/mcp
MCP server metadata
- Name
- champfy-chatgpt-app
- Version
- 0.1.0
Known tools 5
render_player_discovery_panelOpen the interactive Champfy player discovery panel beside the conversation.
Inferred read-onlyestimate_skill_levelEstimate a tennis skill level from Champfy quiz answers and return a rationale.
Inferred read-onlyget_tennis_skill_quizReturn the Champfy tennis skill self-assessment quiz as structured JSON (question and choice ids for use with estimate_skill_level).
Inferred read-onlyrender_tennis_skill_quizMount the interactive tennis skill self-assessment widget in ChatGPT (MCP Apps UI).
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.champfy-chatgpt-app]
url = "https://www.champfy.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"champfy-chatgpt-app": {
"type": "http",
"url": "https://www.champfy.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: champfy-chatgpt-app
Remote MCP URL: https://www.champfy.com/api/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": {
"champfy-chatgpt-app": {
"url": "https://www.champfy.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"champfy-chatgpt-app": {
"type": "http",
"url": "https://www.champfy.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "champfy-chatgpt-app",
"transport": "streamable-http",
"url": "https://www.champfy.com/api/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.