handigraphs-stats-api-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HANDIGRAPHS_API_KEY | Yes | Bearer key for protected data. It is never accepted as a tool argument. | |
| HANDIGRAPHS_API_BASE_URL | No | API v1 root. HTTPS is mandatory except loopback HTTP used by tests. | https://handigraphs.com/api/v1 |
| HANDIGRAPHS_HTTP_TIMEOUT_MS | No | Upstream request timeout. | 10000 |
| HANDIGRAPHS_MAX_RESPONSE_BYTES | No | Maximum declared or streamed upstream JSON response size. | 5242880 |
| HANDIGRAPHS_DISCOVERY_TTL_SECONDS | No | In-process public-discovery cache TTL. | 300 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_resourcesB | List live sports and stats resources from public Handigraphs discovery. |
| describe_resourceB | Return live resource, metric, split, unit, and filter discovery. |
| query_statsA | Query one live Handigraphs Stats API resource. Use describe_resource first; pagination remains in this tool via cursor. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool serves a distinct function: discovery (list), introspection (describe), and data access (query). There is no overlap in their purposes, and the descriptions make it clear when to use each.
All tool names follow a consistent verb_noun pattern (list_resources, describe_resource, query_stats). The naming is predictable and reinforces the workflow.
Three tools is an ideal size for this server's scope: discover, understand, and query. Each tool is necessary and none feel redundant or missing.
The tool set provides a complete workflow for a stats API client: listing available resources, getting detailed descriptions, and querying with pagination support. There are no obvious gaps for the stated purpose.