A
licenseNot graded
qualityA
maintenanceEnables submission, tracking, and retrieval of governed tasks from DeepSeek Harness against BailingHub routes, allowing job management without opening embedded chat interfaces.
245 npm
2
MIT
bailinghub-mcp-server
Officialby bailinghub
Related Servers
Alternatives to bailinghub-mcp-server
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables MCP clients to securely execute bounded coding tasks through registered backends, with idempotent job submission, status polling, and artifact retrieval. It isolates each job in Git worktrees and supports optional branch publishing and pull request creation under strict policy constraints.-
- AlicenseAqualityDmaintenanceEnables programmatic interaction with Opus workflow automation platform, allowing users to initiate jobs, execute workflows, monitor status, upload files, and retrieve results through the Opus Job Operator API.7MIT
- FlicenseCqualityCmaintenanceEnables stdio-capable MCP clients to run governed enterprise operations tasks, including policy/runbook retrieval and ticket and user lookups or writes. High-risk actions are held for human approval and role-based access is enforced server-side, so clients cannot bypass governance.41-
- AlicenseNot gradedqualityBmaintenanceEnables coordinating specialist agents through an event-driven backend, allowing submission of goals, retrieval of job status and results, and listing of jobs via MCP tools.MIT
- AlicenseAqualityAmaintenanceEnables orchestrator agents to route coding tasks to native CLI worker agents via MCP, providing tools for agent discovery, task submission, waiting, inspection, and cancellation.53MIT
TDQS
A4.4/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: submitting a job, reading its current state, and polling until completion. Even though get and wait both read state, wait explicitly adds bounded polling behavior, so an agent can easily choose the right one.
Naming Consistency5/5
All tool names follow a consistent verb_governed_job pattern: submit_, get_, wait_for_. This makes the set predictable and easy to learn.
Tool Count5/5
Three tools is well-scoped for a narrow domain of submitting and monitoring a governed job. There is no bloat or redundancy.
Completeness5/5
The tool surface covers the full lifecycle for a client: submit the action, retrieve its state, and wait for a result. No obvious operations are missing for the stated purpose.
Maintenance
ActivityActive
ResponsivenessNo issues