codechef-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_profileA | Fetch a CodeChef user's profile as compact structured JSON: name, star rating, current and highest rating, division, global rank, country rank, problems solved, contests participated, latest contest and recent form. Prefer this over downloading and parsing the profile HTML page. |
| get_rating_historyA | Return a user's contest rating history (newest first) with rating after each contest, rating change (delta) and rank. Useful for trends, streaks and 'how has X improved' questions. |
| get_activityA | Summarize a user's submission heat map over a time window: total submissions, active days, average per active day, busiest day and monthly totals. Answers 'how active is X' without loading the heat map image or HTML. |
| get_contestsA | List a user's contests (newest first) with the problems solved in each, plus rank and rating change where available. Use this for 'what has X solved recently' or per-contest performance. |
| get_solved_problemsA | Return the unique problem names a user has solved (as listed on their profile), with the contest each came from, plus their reported total solved count. Capped by 'limit' to protect context size. |
| compare_usersA | Fetch compact side-by-side profiles for 2-5 CodeChef handles: rating, stars, ranks, problems solved and contest count. Handy for 'who is better' or team-selection questions. |
| open_contestA | Open a CodeChef contest, fetch problem list, start/end dates, and contest metadata. |
| list_problemsA | List all problems in a CodeChef contest with codes, names, and submission counts. |
| get_problemA | Fetch full problem statement, constraints, time/memory limits, and sample test cases. |
| validate_complexityB | Estimate time and space complexity of code through static loop analysis and comment annotations. |
| generate_testsA | Generate adversarial and edge-case test inputs (minimums, maximums, duplicates, sorted, random) for a problem. |
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 11 tools
Tools mostly target distinct facets: profile, rating history, activity, contests, solved problems, contest problem access, and code analysis. Some overlap exists between open_contest and list_problems for contest problem lists, and between get_rating_history and get_contests for per-contest rating data, but descriptions largely clarify intended use.
All tool names use snake_case and follow a predictable verb_noun or verb_noun_plural pattern, such as get_profile, list_problems, compare_users, and generate_tests. There are no mixed casing styles or vague names.
With 11 tools, the server is well-scoped for CodeChef profile, contest, and problem analysis. The count is neither thin nor bloated, and each tool has a plausible role.
The surface covers the major read-only workflows: profiles, rating trends, activity, contests, solved problems, comparisons, contest problems, complexity validation, and test generation. Minor gaps include global problem search, submission/code retrieval, and contest leaderboards, but core workflows are supported.