kintsugi
Related Servers
Alternatives to kintsugi
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to compile polyglot repositories into architectural mipmap containers and use stateful pre-edit guardrails, fog-of-war resolution gating, blast-radius analysis, and compact Markdown packets to inspect code and prevent unsafe edits.Apache 2.0
- AlicenseAqualityCmaintenanceEnables coding agents to check whether a repository already provides the helper they are about to reimplement, surface bloat, missing error handling and security findings after each edit, and block task completion until blocking issues are fixed.7MIT
- AlicenseAqualityBmaintenanceConnects AI coding assistants to QA engineering standards, regulatory checklists, and a preflight audit engine. Enables skill discovery and installation, license verification, and safe project inspection with human-in-the-loop confirmation.92,201 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to turn human-verified development failures into reusable bug knowledge and executable acceptance standards, then generate graded verification plans and record structured evidence for human review.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to capture observable workflows, distill successful techniques and failure lessons into evidence-linked versioned skills, evaluate and approve them through review gates, and distribute approved instructions and portable resources through MCP for reuse across tasks.MIT
- AlicenseNot gradedqualityBmaintenanceEnables diagnosis of recurring coding-agent loop failures from clean, local, zero-telemetry traces and proposes small, reversible fixes to verifiers, retry policies, stop conditions, or skills that are applied only after explicit approval.Apache 2.0
TDQS
Scored across 4 tools
Each tool owns a distinct stage of the scar lifecycle: scanning code (kintsugi_scan_code), browsing the catalog (kintsugi_list_scars), authoring a new scar (kintsugi_record_failure), and exporting to skill files (kintsugi_compile_skills). The scan-vs-list boundary is clearly separated by input (code snippet/path vs catalog filters), so an agent can pick correctly without ambiguity.
All four tools use the identical `kintsugi_` namespace plus a verb_noun pattern (scan_code, list_scars, record_failure, compile_skills). No casing or verb-style deviation anywhere in the set.
Four tools is a tight, well-scoped surface for a scar knowledge-base server, and each one maps to a distinct workflow step with no filler or redundancy. Nothing feels missing at the count level; the gaps are lifecycle operations, not volume.
The create (record_failure) → read (list_scars) → apply (scan_code) → distribute (compile_skills) pipeline is coherent, but there is no way to update, deprecate, or delete an existing scar once persisted to scars.json. An agent that records a bad or stale scar has no dead-end-free path to correct it.