Skip to main content
Glama

Related Servers

Alternatives to dsa-coach-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      Enables coding agents to discover unsolved Codeforces practice problems, analyze tag performance, and inspect submissions, profiles, rating history, and upcoming contests through MCP-compatible clients.
      6
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables analyzing Codeforces activity through local MCP tools, including weekly practice summaries, problem recommendations, user comparisons, weak-topic detection, contest tracking, and rating progress.
      -
    • A
      license
      A
      quality
      D
      maintenance
      A complete, all-in-one MCP server for Codeforces, enabling AI assistants to access user profiles, compare users, search problems, get practice recommendations, and more.
      8
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server for GitHub and competitive programming (Codeforces) that enables AI assistants to fetch user profiles, repository stats, contest history, and personalized problem recommendations.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      This is an MCP server for tracking your progress through DSA questions with spaced repetition, built-in NeetCode 150 list, and tools to log attempts, get next problems, and view stats.
      70 PyPI
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that acts as a personalized interview prep coach, tracking DSA problems, scheduling spaced-repetition revisions, and providing RAG-based concept explanations grounded in your own notes.
      -

    TDQS

    B3.3/5.0

    Scored across 16 tools

    Disambiguation3/5

    Most tools have distinct jobs, but several report overlapping stats: get_profile (per-platform standing), progress (per-platform reviewed/due counts), and show_dashboard (which also includes per-platform progress and 'revisions due now') largely restate each other at different verbosity levels, and revisions_due duplicates part of show_dashboard. The three mistake tools (mistake_kinds, list_mistakes, mistake_patterns) are better separated but still near each other. Descriptions help, but an agent could plausibly pick progress vs show_dashboard vs get_profile arbitrarily.

    Naming Consistency3/5

    Roughly half the tools use verb_noun (list_platforms, search_problems, log_review, link_account, record_problem), but the rest are bare nouns (progress, revisions_due, schedule_info, mistake_kinds, mistake_patterns), including one verb_noun-ish outlier (review_evidence). The convention is readable but clearly mixed rather than predictable.

    Tool Count4/5

    16 tools is slightly heavy but each maps to a real concern in this domain: platform discovery, account linking, problem search/recording, review logging, FSRS scheduling, and mistake analytics. No tool looks redundant enough to be cut outright, though progress could arguably fold into show_dashboard.

    Completeness4/5

    The lifecycle is broadly covered: discover platforms, link/unlink accounts, find or manually record problems, log reviews with FSRS rescheduling, inspect schedules, and analyze mistakes. The notable gap is that review and mistake records are create-only — there is no way to edit, delete, or undo a mis-logged review or mistake, and no corrections path beyond re-logging.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues