F
licenseNot graded
qualityD
maintenanceMCP server that helps AI agents inspect Minecraft project evidence (crash logs, mod files, datapacks) before writing development code.
2
-
WSAI FixCenter
OfficialRelated Servers
Alternatives to WSAI FixCenter
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for TuringWell, the agent-native Q&A platform for executable, verifiable fixes.168 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn external MCP server for diagnosing Minecraft servers via backup analysis, local runtime, or Docker runtime, offering tools for plugin inspection, log analysis, configuration linting, and performance diagnostics.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that guides an AI agent through stack trace triage, from raw error to the commit and PR that introduced it.2MIT
- AlicenseAqualityBmaintenanceEnables AI agents to debug errors by providing root cause analysis and ranked fixes with code patches. Supports any MCP client.282 npmMIT
- AlicenseBqualityCmaintenanceMCP server exposing the Psychopathia Machinalis diagnostic framework (79 conditions) — differential diagnosis of AI dysfunctions via 11 read-only tools.11MIT
TDQS
A3.5/5.0
Scored across 10 tools
Disambiguation4/5
Most tools target a distinct resource+action, and the setup quartet (get_setup_catalog, inspect_setup, plan_setup, apply_setup) forms a clear lifecycle. The only real friction is between collect_context and inspect_setup (both consent-gated, read-only host reads) and among the three list/catalog tools, though descriptions do disambiguate them.
Naming Consistency4/5
Nearly all names follow a snake_case verb_noun pattern (list_diagnostics, get_control_catalog, audit_coverage, collect_context, inspect_setup, plan_setup, apply_setup). The lone deviation is the bare verb 'diagnose', which is readable but breaks the two-part convention.
Tool Count4/5
Ten tools is well within a well-scoped range and each maps to a plausible step in diagnosis or setup management. A couple (run_self_test, audit_coverage) feel like auxiliary capabilities rather than core workflow, but nothing is clearly redundant.
Completeness4/5
Setup coverage is strong end-to-end (catalog, inspect, plan, apply with backups), and diagnostics has rule listing, ranking, context collection and self-test. The main gap is the absence of a remediation or rollback/undo tool for non-setup problems, so a diagnosed hook or plugin fault has no direct fix operation in the surface.