Skip to main content
Glama
RichardHu6666

deepseek_harness

by RichardHu6666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to deepseek_harness

No user-submitted related servers found.

    Related Servers

    • hanako-codex-bridge

      TheEarlyWinter
      F
      license
      Not graded
      quality
      B
      maintenance
      A local stdio MCP server that lets Hanako and Codex delegate one-off or persistent text tasks to each other, check local service and executable status, and manage bounded concurrent delegations without exposing tokens or paths.
      -

    • Vibechemy

      DiamondAlchemy
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server for orchestrating a fleet of CLI coding agents in isolated git worktrees. It exposes tools for spawning workers, sending instructions, reviewing diffs, and merging changes, with full terminal visibility.
      3 npm
      4
      MIT

    • Orchestration MCP

      dufangshi
      F
      license
      A
      quality
      D
      maintenance
      A TypeScript MCP server for launching, tracking, and managing external coding-agent runs across local and remote backends like Codex and Claude Code. It allows top-level agents to orchestrate subagents through tools for spawning tasks, polling events, and handling interactive sessions.
      7
      2
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct lifecycle action: start (submit_task), read (get_task), wait (wait_task), interact (continue_task), and stop (cancel_task). The descriptions clarify subtle differences such as immediate read versus waiting for events, and starting a new task versus continuing an existing session.

    Naming Consistency5/5

    All five tool names follow a consistent snake_case verb_noun pattern: submit_task, get_task, wait_task, continue_task, cancel_task. There are no deviations or mixed conventions.

    Tool Count5/5

    Five tools is well-scoped for a task harness, covering the essential lifecycle operations (start, monitor, wait, continue, cancel) without redundancy or missing core actions. Each tool earns its place.

    Completeness4/5

    The core task lifecycle is covered: submission, status retrieval, waiting, feedback continuation, and cancellation. However, there is no list_tasks operation to discover queued or running tasks, and no delete/archive operation, which are minor gaps that agents can work around if task IDs are known.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources