Deed
OfficialRelated Servers
Alternatives to Deed
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceAgent-first programming language: agents produce JSON AST, the compiler validates, type-checks, effect-checks, verifies contracts via Z3/SMT, and compiles to WASM. 19 MCP tools for the full compile-and-execute loop.22232 npm11MIT
- AlicenseAqualityBmaintenanceRetired snapshot of the former 15-tool Apache-2.0 beta. Use Living Stack Community for the free seven-tool proof edition; Complete Local is the paid runtime with memory, recovery, signed traces, release verification, and multi-agent workflows.14Apache 2.0
- AlicenseCqualityBmaintenanceLocal-first MCP runtime for coding agents with bounded workspace access, content-preconditioned writes, AST search, LSP navigation and diagnostics, and Git status/diff. Designed to give coding agents useful repository access without treating unrestricted shell access as the default integration boundary.2132MIT
- AlicenseBqualityBmaintenanceA local, evidence-driven MCP runtime and control plane for open-source maintainers that provides workspace-bounded tools including controlled file operations, command execution, validation primitives, durable execution records, and human review workflows via stdio and Streamable HTTP transports.33MIT
- AlicenseAqualityAmaintenanceCoordination protocol for parallel coding agents, built above Git. The MCP server exposes the full 17-tool lifecycle over stdio: register agents, publish intents with semantic scopes and declared operations, claim work, check for conflicts before code is written, publish ChangeSets, run trusted named verification checks, and record accepted work. Deterministic rules raise findings when two agents'18504Apache 2.0
- AlicenseNot gradedqualityCmaintenanceLocal-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.1MIT
TDQS
Scored across 7 tools
Each tool targets a distinct operation in the Deed toolchain: static checking, test execution, running main, formatting, auto-fixing, diagnostic explanation, and patch review. There is no overlap in their inputs or outputs, so an agent can reliably select the right tool for a given task.
All tools share the `deed_` prefix and a simple verb-based naming scheme (check, test, run, fmt, fix, explain, review). The only minor inconsistency is the abbreviation 'fmt' instead of 'format', but the pattern is otherwise uniform and predictable.
Seven tools is well within the ideal range for a domain-specific language server. Each tool covers a core workflow step (check, test, run, format, fix, explain, review) and none are superfluous or redundant.
The set provides a complete lifecycle for interacting with Deed programs: static checking, testing, execution, formatting, automated repair, diagnostic explanation, and change review. No obvious essential operation is missing; the only conceivable additions (e.g., a build tool) fall outside the apparent scope of this server.