Interactive Leetcode MCP

An MCP server enabling guided DSA learning with AI on leetcode.com

MCP Servers TypeScript Listed MIT

Is Interactive Leetcode MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.3 / 10
Provenance Attested
Signed commits 60%
Last push 11d ago
Compare Interactive Leetcode MCP
Suggest a correction

In detail: Interactive Leetcode MCP scores 73.8/100 (Grade B), ranked #245 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.3/10; 60% of recent commits are signed; last pushed 2026-09-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How Interactive Leetcode MCP compares in MCP Servers

  1. #144 Monarch MCP Server 74.1 +0.3
  2. #145 Freshcontext MCP 73.9 +0.1
  3. #146 Interactive Leetcode MCP 73.8 this agent
  4. #147 Yantrikdb MCP 73.8 ±0
  5. #148 Search Console MCP 73.7 −0.1

Bars show each HVTrust score; the tick marks Interactive Leetcode MCP’s 73.8.

Where the 73.8 comes from

HVTrust dimensions vs the MCP Servers average

73.8 / 100 · 100.0% confidence

Interactive Leetcode MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.1 / 25
6.8 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.0 / 17
0.8 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
14.6 / 20
2.5 above avg 12.1
AdoptionLog-scaled stars · package downloads
5.4 / 20
1.8 below avg 7.2

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-24
Rank Moved
Rank rose 44 spots (#286 → #242)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.3/10. Tighten the weakest checks to improve public safety evidence.
43.6
Activity sub-score · out of 100
#146

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 11 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
12
Forks
3
Last Push
2026-09-15
11 days ago
Commits (4 wk)
6
Downloads (7d)
102
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲4
was #249

Analysis

Activity Inputs

43.6 / 100
StarsRepository reach
6.7 / 30
FreshnessLast push recency
23.5 / 25
ActivityRecent commits
10.5 / 25
CommunityFork signal
2.8 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
5.3 / 10
OpenSSF Scorecard · scanned Sep 19, 2026
Signed Commits
60%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 8
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 6
Packaging 10
Pinned-Dependencies 3
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Common questions about Interactive Leetcode MCP

Interactive Leetcode MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Interactive Leetcode MCP publish package provenance?
Yes. Interactive Leetcode MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Interactive Leetcode MCP have an OpenSSF Scorecard?
Interactive Leetcode MCP has an OpenSSF Scorecard score of 5.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Interactive Leetcode MCP actively maintained?
Maintained. Last push was 11 days ago.
What license does Interactive Leetcode MCP use?
Interactive Leetcode MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Interactive Leetcode MCP's commits signed?
60% of the last 100 commits to Interactive Leetcode MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Interactive Leetcode MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Interactive Leetcode MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Interactive Leetcode MCP?

For maintainers

HVTrust scores Interactive Leetcode MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 23HVTrust 4Grade 3Listed 2Scorecard 1Score 1Delisted 1Provenance 1MCP 1Surface 1Surface 1
2026-09-24
Rank Moved
Rank rose 44 spots (#286 → #242)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 639 spots (#925 → #286)
2026-09-23
HVTrust Changed
HVTrust up 46.0pts (26.3 → 72.3)
2026-09-22
Newly Listed
First tracked at rank #925
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank dropped 14 spots (#270 → #284)
2026-09-16
Rank Moved
Rank dropped 39 spots (#229 → #268)
2026-09-15
Rank Moved
Rank rose 148 spots (#377 → #229)
2026-09-15
HVTrust Changed
HVTrust up 7.1pts (67.7 → 74.8)
2026-09-15
Activity Score Changed
Activity score up 18pts (27 → 45)
2026-09-11
Scorecard Added
OSSF Scorecard: 5.6/10
2026-09-11
Grade Changed
Trust grade C → B
2026-09-11
Rank Moved
Rank rose 356 spots (#718 → #362)
2026-09-11
HVTrust Changed
HVTrust up 11.8pts (56.2 → 68.0)
2026-09-10
Rank Moved
Rank dropped 16 spots (#702 → #718)
2026-09-08
Rank Moved
Rank dropped 12 spots (#683 → #695)
2026-09-07
Rank Moved
Rank dropped 50 spots (#633 → #683)
2026-09-06
Grade Changed
Trust grade D → C
2026-09-06
Rank Moved
Rank rose 497 spots (#1130 → #633)
2026-09-06
HVTrust Changed
HVTrust up 19.1pts (38.0 → 57.1)
2026-09-05
Rank Moved
Rank dropped 36 spots (#1094 → #1130)
2026-09-04
Rank Moved
Rank dropped 23 spots (#1071 → #1094)
2026-09-03
Rank Moved
Rank dropped 57 spots (#1014 → #1071)
2026-09-02
Rank Moved
Rank dropped 44 spots (#970 → #1014)
2026-09-01
Rank Moved
Rank dropped 44 spots (#926 → #970)
2026-08-31
Rank Moved
Rank dropped 27 spots (#899 → #926)
2026-08-30
Rank Moved
Rank dropped 41 spots (#858 → #899)
2026-08-29
Rank Moved
Rank dropped 45 spots (#813 → #858)
2026-08-28
Rank Moved
Rank dropped 23 spots (#790 → #813)
2026-08-27
Rank Moved
Rank dropped 24 spots (#766 → #790)
2026-08-26
Rank Moved
Rank dropped 106 spots (#660 → #766)
2026-08-16
Rank Moved
Rank dropped 13 spots (#644 → #657)
2026-08-10
Rank Moved
Rank dropped 20 spots (#615 → #635)
2026-08-08
Newly Listed
First tracked at rank #611

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 73.8 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/interactive-leetcode-mcp.svg)](https://hvtracker.net/agents/interactive-leetcode-mcp)
HTML:
<a href="https://hvtracker.net/agents/interactive-leetcode-mcp"><img src="https://hvtracker.net/badge/interactive-leetcode-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON