A
licenseA
qualityC
maintenanceEnables interactive LeetCode practice with AI-guided authentication, problem solving, solution submission, and learning mode.
24
62 npm
12
MIT
LeetCode CN MCP
by lkastar
Related Servers
Alternatives to LeetCode CN MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables Claude to search and retrieve LeetCode problems, user profiles, and statistics through natural language.-
- AlicenseNot gradedqualityBmaintenanceEnables Claude to fetch and analyze your public LeetCode submission history, weak areas, and daily challenge via a remote MCP server.8 npmMIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that provides integration with LeetCode APIs, enabling automated interaction with programming problems, contests, solutions, and user data across both leetcode.com and leetcode.cn platforms.9177 npm149MIT
- FlicenseNot gradedqualityCmaintenanceEnables querying a personal GitHub repository of solved LeetCode problems via natural language, including topic-based search and live retrieval of solution code with difficulty and tags.1-
- AlicenseNot gradedqualityAmaintenanceEnables interaction with public NowCoder ACM problem pages. Supports fetching problem data and checking health status.MIT
TDQS
A3.9/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clear, non-overlapping responsibility: authentication lifecycle (login, logout, auth_status), problem lookup (get_problem), and submission history retrieval (get_submissions_by_date). There is no realistic ambiguity between tool purposes.
Naming Consistency4/5
Most tools follow a readable snake_case pattern with clear verbs and nouns, such as get_problem and get_submissions_by_date. login/logout and auth_status are minor deviations but remain conventional and predictable.
Tool Count5/5
Five tools is well-scoped for a focused LeetCode CN server handling authentication, problem data, and submission history. Each tool earns its place with no redundancy or bloat.
Completeness4/5
Authentication status/login/logout form a complete lifecycle, and problem fetching plus daily submission retrieval cover the core read-only workflows. Minor gaps such as broader problem search or submission detail endpoints are workable but not critical.
Maintenance
ActivityMaintained
ResponsivenessNo issues