pc-diag
Related Servers
Alternatives to pc-diag
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides Windows system diagnostic capabilities to AI agents, allowing them to access event logs, crash information, system uptime, and perform stability analysis.113MIT
- AlicenseAqualityCmaintenanceEnables AI agents to safely query and manage Windows services, processes, event logs, and system information, with write actions disabled by default.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only inspection and diagnosis of Windows, macOS, and Linux machines through eight diagnostic tools covering system profiles, baselines, disk health, startup audits, driver context, and upgrade planning, with voice summaries and a web simulator. It enforces an R0-R3 risk model in code so only safe R0 evidence collection is automatic while riskier actions remain manual guidance.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to investigate a live machine or evidence files for signs of compromise, collecting read-only evidence and requiring findings to cite real evidence IDs.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT to safely inspect bounded Windows diagnostic evidence and verify system changes through deterministic before/after snapshots.MIT
- AlicenseNot gradedqualityCmaintenanceGives AI clients read-first access to Windows processes, services, startup apps, disk usage, GPU/CPU/memory stats, and allowlisted read-only PowerShell commands without any screen or cursor control. State-changing actions such as starting or killing processes are gated behind an explicit confirmation flag.MIT
TDQS
Scored across 8 tools
Most tools have a clear, distinct diagnostic role. The main overlap is list_tdr_incidents versus query_events (pre-classified incident summary vs raw log query), and driver version appears in system_info, driver_inventory, and dxdiag_summary, but descriptions explicitly guide when to use each.
All names are snake_case and readable, but there is no single predictable pattern: list/query/describe are verb-first, while system_info, process_snapshot, sensor_snapshot, driver_inventory, and dxdiag_summary are noun-first. This mixed convention is understandable but not fully consistent.
Eight tools is well within the typical 3-15 range for a diagnostic server. Each tool covers a distinct layer (time/system baseline, incidents, raw events, live state, sensors, drivers, DirectX, collection disclosure) and no obvious redundant member bloats the set.
The core crash/GPU diagnostic workflow is covered from time normalization through incident detection, raw event evidence, live process/sensor state, driver inventory, and DirectX details. Minor gaps remain around deeper dump-file inspection, storage health/SMART, and broader hardware/service inventory, but the primary diagnostic path has no major dead end.