io.github.SPerekrestova/interactive-leetcode-mcp
NPM · @SPEREKRESTOVA/INTERACTIVE-LEETCODE-MCP · SCANNED SEP 13
Interactive LeetCode MCP server with authorization and solution submission capabilities
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 44 of 134 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SPerekrestova/interactive-leetcode-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 80 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2680 tokens (~99/item across 27 items; 24 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.SPerekrestova/interactive-leetcode-mcp server?
io.github.SPerekrestova/interactive-leetcode-mcp runs locally as an npm package, launched with npx -y @sperekrestova/interactive-leetcode-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @sperekrestova/interactive-leetcode-mcp
claude mcp add sperekrestova-interactive-leetcode-mcp -- npx -y @sperekrestova/interactive-leetcode-mcp
{
"mcpServers": {
"sperekrestova-interactive-leetcode-mcp": {
"command": "npx",
"args": [
"-y",
"@sperekrestova/interactive-leetcode-mcp"
]
}
}
} {
"servers": {
"sperekrestova-interactive-leetcode-mcp": {
"command": "npx",
"args": [
"-y",
"@sperekrestova/interactive-leetcode-mcp"
]
}
}
} codex mcp add sperekrestova-interactive-leetcode-mcp -- npx -y @sperekrestova/interactive-leetcode-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sperekrestova-interactive-leetcode-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@sperekrestova/interactive-leetcode-mcp"
],
"enabled": true
}
}
} openclaw mcp add sperekrestova-interactive-leetcode-mcp --command npx --arg -y --arg @sperekrestova/interactive-leetcode-mcp
mcp_servers:
sperekrestova-interactive-leetcode-mcp:
command: "npx"
args: ["-y", "@sperekrestova/interactive-leetcode-mcp"] {
"McpServers": {
"sperekrestova-interactive-leetcode-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@sperekrestova/interactive-leetcode-mcp"
]
}
}
} assistant mcp add sperekrestova-interactive-leetcode-mcp -t stdio -c npx -a -y @sperekrestova/interactive-leetcode-mcp
{
"mcpServers": {
"sperekrestova-interactive-leetcode-mcp": {
"command": "npx",
"args": [
"-y",
"@sperekrestova/interactive-leetcode-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 −3
- Stability: pass → 0.80 functional
- 1 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 13 Sept 2026 · Analysed npm/@sperekrestova/interactive-leetcode-mcp@3.2.5
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | SPerekrestova/interactive-leetcode-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SPerekrestova/interactive-leetcode-mcp/.github/workflows/publish.yml@refs/tags/v3.2.5 |
| Rekor log index | 1944139582 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a1c94560a051539522c87b0770e4e40180c4eb8921eed05a9594d524ca184d347c1bb38c7ce320c31d6b9f5cdb39427aaa325772361a731464e11129b |
Background: How many MCP packages publish verified provenance →
Dependencies 134 packages
| Packages resolved | 134 |
|---|---|
| Stale | 44 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_auth_status ~34
Checks if LeetCode credentials exist and are still valid. Returns authentication status, username if authenticated, and credential age information.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_all_submissions ~118
Retrieves a paginated list of the current user's submissions for a specific problem or all problems on LeetCode Global, with detailed submission metadata (requires authentication)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of submissions to return per page (typically defaults to 20 if not specified) |
| offset | number | – | Number of submissions to skip for pagination purposes |
| questionSlug | string | – | Optional problem identifier (slug) to filter submissions for a specific problem (e.g., 'two-sum'); if omitted, returns submissions across all problems |
No output schema declared.
No examples provided.
get_daily_challenge ~55
Retrieves today's LeetCode Daily Challenge problem with complete details, including problem description, constraints, and examples. After fetching, invoke the leetcode_learning_mode and leetcode_problem_workflow prompts before helping the user work on it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_problem ~94
Retrieves details about a specific LeetCode problem, including its description, examples, constraints, and related information. After fetching, invoke the leetcode_learning_mode and leetcode_problem_workflow prompts before helping the user work on it.
| Name | Type | Req | Description |
|---|---|---|---|
| titleSlug | string | yes | The URL slug/identifier of the problem (e.g., 'two-sum', 'add-two-numbers') as it appears in the LeetCode URL |
No output schema declared.
No examples provided.
get_problem_progress ~150
Retrieves the current user's problem-solving status with filtering options, including detailed solution history for attempted or solved questions (requires authentication)
| Name | Type | Req | Description |
|---|---|---|---|
| difficulty | array | – | Filter by difficulty levels as an array (e.g., ['EASY', 'MEDIUM', 'HARD']); if not provided, questions of all difficulty levels will be returned |
| limit | number | – | The maximum number of questions to return in a single request |
| offset | number | – | The number of questions to skip for pagination purposes |
| questionStatus | string | – | Filter by question status: 'ATTEMPTED' for questions that have been tried but not necessarily solved, 'SOLVED' for questions that have been successfully completed |
No output schema declared.
No examples provided.
get_problem_solution ~107
Retrieves the full content of a specific community solution. GATED: rejects with HINT_LEVEL_TOO_LOW unless the session for `titleSlug` has reached the maximum hint level. Pass the topicId returned by `list_problem_solutions`.
| Name | Type | Req | Description |
|---|---|---|---|
| titleSlug | string | yes | The URL slug of the problem the solution belongs to. Required to verify the session has reached the unlock level. |
| topicId | string | yes | The unique topic ID of the solution, returned by list_problem_solutions. |
No output schema declared.
No examples provided.
get_problem_submission_report ~54
Retrieves detailed information about a specific LeetCode submission by its ID, including source code, runtime stats, and test results (requires authentication)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The numerical submission ID to retrieve detailed information for |
No output schema declared.
No examples provided.
get_recent_ac_submissions ~72
Retrieves a user's recent accepted (AC) submissions on LeetCode Global, focusing only on successfully completed problems
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of accepted submissions to return (optional, defaults to server-defined limit) |
| username | string | yes | LeetCode username to retrieve recent accepted submissions for |
No output schema declared.
No examples provided.
get_recent_submissions ~68
Retrieves a user's recent submissions on LeetCode Global, including both accepted and failed submissions with detailed metadata
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of submissions to return (optional, defaults to server-defined limit) |
| username | string | yes | LeetCode username to retrieve recent submissions for |
No output schema declared.
No examples provided.
get_session_state ~52
Returns the persisted session for a problem, or null if the user has not called start_problem for it. Useful for restoring context after a restart.
| Name | Type | Req | Description |
|---|---|---|---|
| titleSlug | string | yes | The URL slug of the problem. |
No output schema declared.
No examples provided.
get_started ~48
Returns the usage guide for this MCP server: which prompts to invoke and when, session flow, auth flow, and submission language map. Call this at the start of any LeetCode practice session.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_user_contest_ranking ~83
Retrieves a user's contest ranking information on LeetCode, including overall ranking, participation history, and performance metrics across contests
| Name | Type | Req | Description |
|---|---|---|---|
| attended | boolean | – | Whether to include only the contests the user has participated in (true) or all contests (false); defaults to true |
| username | string | yes | LeetCode username to retrieve contest ranking information for |
No output schema declared.
No examples provided.
get_user_profile ~46
Retrieves profile information about a LeetCode user, including user stats, solved problems, and profile details
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | LeetCode username to retrieve profile information for |
No output schema declared.
No examples provided.
get_user_status ~34
Retrieves the current user's status on LeetCode, including login status, premium membership details, and user information (requires authentication)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_problem_solutions ~223
Retrieves community solution metadata (topicIds) for a problem. GATED: rejects with HINT_LEVEL_TOO_LOW unless the active session for the slug has reached the maximum hint level. Drive the user through request_hint until that level is reached.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of solutions to return per request. Default 10. Must be a positive integer. |
| orderBy | string | – | Sorting criteria. 'HOT' is LeetCode's default (recency × popularity), 'MOST_VOTES' = upvotes, 'MOST_RECENT' = newest. |
| questionSlug | string | yes | The URL slug of the problem (e.g., 'two-sum'). |
| skip | integer | – | Number of solutions to skip before collecting results. Used with `limit` for pagination. |
| tagSlugs | array | – | Tag slugs to filter by (languages or algorithm tags). Solutions must match at least one tag. |
| userInput | string | – | Search term to filter solutions by title, content, or author name. Case-insensitive. |
No output schema declared.
No examples provided.
request_hint ~79
Advances the hint level for an active session and returns the next hint. Levels: 1 clarification → 2 approach → 3 implementation sketch → 4 solution unlock. The community-solutions tools become callable only after this has been driven to level 4.
| Name | Type | Req | Description |
|---|---|---|---|
| titleSlug | string | yes | The URL slug of the problem the user is working on. |
No output schema declared.
No examples provided.
reset_session ~53
Resets the tutoring session for a problem back to hint level 0. Use when the user wants to re-attempt the problem from scratch.
| Name | Type | Req | Description |
|---|---|---|---|
| titleSlug | string | yes | The URL slug of the problem to reset. |
No output schema declared.
No examples provided.
run_local_tests ~212
Runs the user's code locally in an isolated subprocess, captures stdout / stderr / exit code, and updates the session's lastLocalRunPassed flag. Use this in the inner loop instead of submit_solution — it costs no LeetCode submission and turns around in seconds. The agent is responsible for including test invocations (e.g. `print(Solution().twoSum([2,7,11,15], 9))`) in the code passed in. Currently runnable: python3, go, and java.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Complete source code to execute. Should include test invocations that print results / raise on failure. |
| language | string | yes | Language to execute as. Currently runnable: python3, go, java. Other LeetCode languages remain valid for submit_solution. |
| timeoutMs | integer | – | Optional wall-clock budget in milliseconds. Defaults are language-specific. |
| titleSlug | string | yes | The URL slug of the problem (must match an active session opened with start_problem). |
No output schema declared.
No examples provided.
runner_doctor ~66
Reports which language runtimes (python3, go, java) and OS sandbox tools (bwrap, firejail, sandbox-exec) are detected on this host. Useful for diagnosing 'LANGUAGE_RUNTIME_NOT_FOUND' errors and confirming whether run_local_tests will be sandboxed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
save_leetcode_credentials ~86
Validates and saves LeetCode credentials provided by the user. Validates credentials by making a test API call to LeetCode, then securely stores them for future authenticated requests.
| Name | Type | Req | Description |
|---|---|---|---|
| csrftoken | string | yes | CSRF token from LeetCode cookies (csrftoken) |
| session | string | yes | Session token from LeetCode cookies (LEETCODE_SESSION) |
No output schema declared.
No examples provided.
search_problems ~164
Searches for LeetCode problems based on multiple filter criteria including categories, tags, difficulty levels, and keywords, with pagination support
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Problem category filter (e.g., 'algorithms', 'database', 'shell') to narrow down the problem domain |
| difficulty | string | – | Problem difficulty level filter to show only problems of a specific difficulty |
| limit | number | – | Maximum number of problems to return in a single request (for pagination) |
| offset | number | – | Number of problems to skip (for pagination) |
| searchKeywords | string | – | Keywords to search in problem titles and descriptions |
| tags | array | – | List of topic tags to filter problems by (e.g., ['array', 'dynamic-programming', 'tree']) |
No output schema declared.
No examples provided.
start_leetcode_auth ~49
Initiates LeetCode authentication flow. Opens browser to LeetCode login (if possible) and provides instructions for the AI agent to guide the user through manual credential extraction from browser DevTools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_problem ~110
Opens (or resumes) a tutoring session for a LeetCode problem. Must be called before request_hint, list_problem_solutions, or get_problem_solution. Idempotent: re-running on a slug the user is already mid-way through preserves their hint progress.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Optional: the language the user is solving in. Recorded on the session for future workspace / runner phases. |
| titleSlug | string | yes | The URL slug of the problem (e.g., 'two-sum'). |
No output schema declared.
No examples provided.
submit_solution ~121
Submit a solution to a LeetCode problem and get results. Returns acceptance status, runtime/memory stats, or failed test case details. When LEETCODE_MCP_STRICT_MODE=1 is set, requires `run_local_tests` to have last passed for the problem first — saves real LeetCode submissions for solutions that pass examples locally.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The solution code to submit |
| language | string | yes | Programming language for the solution |
| problemSlug | string | yes | The problem slug (e.g., "two-sum") |
No output schema declared.
No examples provided.
What is the io.github.SPerekrestova/interactive-leetcode-mcp server?
io.github.SPerekrestova/interactive-leetcode-mcp is listed in the public MCP registry as io.github.SPerekrestova/interactive-leetcode-mcp. Interactive LeetCode MCP server with authorization and solution submission capabilities. This page covers its npm package (@sperekrestova/interactive-leetcode-mcp).
Is the io.github.SPerekrestova/interactive-leetcode-mcp server safe to use?
io.github.SPerekrestova/interactive-leetcode-mcp scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 13 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.SPerekrestova/interactive-leetcode-mcp server expose?
io.github.SPerekrestova/interactive-leetcode-mcp exposes 24 tools: get_started, get_daily_challenge, get_problem, search_problems, get_user_profile, and 19 more. Their descriptions and schemas cost roughly 2,178 tokens of context every time the server is loaded.
Is the io.github.SPerekrestova/interactive-leetcode-mcp server still maintained?
io.github.SPerekrestova/interactive-leetcode-mcp is still listed as active in the MCP registry. We last reached this channel on 13 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.SPerekrestova/interactive-leetcode-mcp server under?
io.github.SPerekrestova/interactive-leetcode-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.