Skip to main content
Glama

Related Servers

Alternatives to uplus-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables users to patrol QingSoft U+ courses, track homework and experiments, read objective questions into structured briefs for a connected MCP client model to answer, fill and verify selections, and optionally submit, while handing subjective, programming, report and file work back to the human.
      9
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to automate icourse163 course workflows, including browser-based login, inspecting course structure, completing task points, submitting quizzes with simulated timing, replying to discussions, and verifying progress.
      13
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an agent to log into the xxt (cx) homework platform, list courses and assignments, read question details with answer-format guidance, and submit answers — optionally as a dry run. Handles login via a real local browser or manually supplied cookies.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to automate course workflows: list courses, scan required tasks, verify server-side completion, extract structured questions, inject answers, inspect per-question and per-option grading, and transcribe media.
      MIT

    TDQS

    B3.2/5.0

    Scored across 38 tools

    Disambiguation3/5

    Most U+ domain tools have distinct intents, but several experiment tools overlap heavily: uplus_read_experiment_detail, uplus_inspect_experiment, uplus_download_experiment_materials, and uplus_audit_experiment all read related experiment data. Similarly, uplus_generate_experiment_report, uplus_answer_experiment, and uplus_submit_experiment_report can be confused, and uplus_inspect_homework/audit_homework/answer_homework/repair_homework form a dense cluster. The detailed descriptions mitigate this, but boundaries are not always obvious at a glance.

    Naming Consistency4/5

    Tool names use two clear, consistent namespaces: uplus_* for domain operations and browse_* for browser primitives, all in snake_case with predictable verb_noun forms. Minor deviations exist, such as the legacy browse_launch_edge spelling and uplus_close as a bare verb, but overall the pattern is easy to follow.

    Tool Count2/5

    At 38 tools, the surface is heavy: 20 domain-specific U+ operations plus 18 generic browser primitives. While some browser tools are useful fallbacks, the generic low-level operations (click, fill, type, press, scroll, eval, snapshot, batch) add substantial weight beyond the core course/homework/experiment workflow.

    Completeness4/5

    The domain surface covers a full lifecycle: login, course listing, homework inspection/answering/auditing/repairing/submitting, experiment inspection/material download/report generation/answering/submission/auditing, plus attachment upload and image capture. Browser primitives provide fallback navigation and interaction. Minor gaps remain, such as a dedicated browser navigation tool outside batch/open, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues