Skip to main content
Glama
OPFIMISS

DS Claude Haha MCP

by OPFIMISS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to DS Claude Haha MCP

No user-submitted related servers found.

    Related Servers

    • ccc-mcp

      Basil155
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an external AI agent to delegate tasks to a local Claude Code installation and receive structured reports, with code modifications governed by a plan-approval-execution workflow and direct file and git operations available outside that loop.
      MIT

    • codex-mcp-opencode

      Ichikawashadow
      A
      license
      A
      quality
      B
      maintenance
      A project-local MCP bridge that allows Codex Desktop to plan tasks and OpenCode to execute them within the current project directory, with session reuse and native OpenCode background subagents.
      4
      1
      MIT

    • mcp-relay

      mhcoen
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude Desktop and Claude Code, enabling autonomous exchange of messages, files, and code while keeping their context windows separate.
      4
      MIT

    • claude_mcp

      catid
      A
      license
      A
      quality
      C
      maintenance
      Bridges Codex to a local Claude Opus 5 collaborator via Claude Code, enabling controlled read-only consultation or write-capable tasks on allowed workspaces with independent verification.
      3
      MIT
    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 6 tools

    Disambiguation4/5

    Each tool has a distinct role: profiles for listing, status for snapshots, start for async initiation, wait for polling, cancel for stopping, and run for full delegation. Start and run overlap slightly in that both initiate tasks, but run is explicitly end-to-end while start is async, making them distinguishable.

    Naming Consistency4/5

    All tools share the deepseek_ prefix, with a mix of nouns (profiles, status) and verbs (start, wait, cancel, run). The pattern is consistent in that getters use nouns and actions use verbs, though a fully consistent verb_noun convention would be clearer.

    Tool Count5/5

    Six tools is well-scoped for managing DeepSeek task delegation: listing options, checking status, starting, waiting, cancelling, and running end-to-end. Each tool earns its place without unnecessary redundancy.

    Completeness4/5

    The surface covers the full lifecycle: profile discovery, async start, status monitoring, waiting for completion, cancellation, and a combined run operation. A minor gap is the lack of an explicit 'list active tasks' tool, but status and wait cover most monitoring needs.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources