PC-Fixer MCP Server
Related Servers
Alternatives to PC-Fixer MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI coding agents to snapshot workspaces, roll back risky changes, diagnose and resolve port conflicts or orphan processes, and generate reproducible execution recipes.25430 npmApache 2.0
- AlicenseBqualityBmaintenanceProvides a universal developer operations and diagnostics toolkit with sandboxed code execution, algorithm stress testing, security secret scanning, AST-based code fixes, and a visual dashboard for ERD, port/process inspection, and differential testing.2836 npm3MIT
- FlicenseAqualityDmaintenanceEnables LLM-driven agents to autonomously detect, diagnose, repair, verify, and prevent software and hardware failures on local and remote systems. Includes built-in safety checks and automatic rollbacks.15-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to perform zero-token static audits, simulate refactorings in an ephemeral RAM clone, trace downstream ripple effects, and block unsafe writes with automatic rollback to prevent regressions.76 npmBusiness Source 1.1
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to securely inspect, modify, and manage local projects with trusted filesystem access, safe Git operations, controlled task execution, and developer runtime process management over stdio or HTTP.4Apache 2.0
- AlicenseBqualityDmaintenanceEnables autonomous infrastructure diagnostics, log root-cause analysis, and safe code patching via tools for querying logs, inspecting Python AST, and applying git-safe patches.3Apache 2.0
TDQS
Scored across 7 tools
Most tools are distinct, but pc_fixer_diagnose explicitly claims to cover 'Git repository locks' and 'CWE vulnerabilities,' directly overlapping with the dedicated pc_fixer_cwe_audit and pc_fixer_clean_git_locks tools. An agent wanting a security scan or git-lock cleanup could reasonably misselect between the broad diagnose tool and the specialized ones, though descriptions do help differentiate.
All tools share a consistent pc_fixer_ prefix and snake_case convention, which is a strong unifying pattern. However, action ordering is mixed (check_system and kill_port_process are verb_noun, while cwe_audit is noun_verb and rollback/diagnose are bare verbs), a minor deviation from a uniform verb_noun scheme.
Seven tools is well within the ideal 3-15 range for a PC/codebase fixing server. Each tool maps to a distinct concern (diagnose, heal, rollback, system health, security audit, port kill, git locks) and earns its place without bloat.
The lifecycle of diagnose -> heal -> rollback is covered, along with system checks and targeted fixes, giving strong overall coverage. The one gap is discoverability of transaction IDs: pc_fixer_rollback requires a transaction ID but there is no tool to list prior healing transactions, forcing reliance on manifests returned by heal.