Windows Diagnostics MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging by setting environment variable to 'mcp:*' | mcp:* |
| NODE_ENV | No | Node environment setting | production |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_system_diagnosticsB | Get comprehensive Windows system diagnostics including crashes, reboots, and system health |
| get_shutdown_eventsC | Get only shutdown and reboot events |
| get_bsod_eventsC | Get Blue Screen of Death (BSOD) events |
| get_system_uptimeB | Get current system uptime and boot information |
| analyze_system_stabilityC | Analyze system stability and provide recommendations |
| search_registryC | Search the Windows registry by keyword |
| analyze_startup_programsB | Analyze startup programs for suspicious entries |
| scan_system_componentsB | Scan system components like services, drivers, and uninstall entries for issues |
| find_orphaned_entriesB | Find orphaned registry entries pointing to non-existent files |
| get_registry_healthC | Get an overall registry health assessment |
| scan_security_risksB | Scan the registry for potential security risks |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes targeting specific diagnostic areas like startup programs, BSOD events, registry health, and system uptime. However, some overlap exists between 'analyze_system_stability' and 'get_system_diagnostics', which could cause confusion as both provide system-wide assessments.
Tool names follow a consistent verb_noun pattern throughout, such as 'analyze_startup_programs', 'get_bsod_events', and 'scan_security_risks'. The only minor deviation is 'find_orphaned_entries', which uses 'find' instead of a more common verb like 'scan' or 'get', but overall naming is highly predictable.
With 11 tools, the count is well-scoped for a Windows diagnostics server, covering various aspects like registry analysis, system events, security, and stability. Each tool appears to serve a specific diagnostic function without redundancy, making the set appropriately sized for the domain.
The tool set provides comprehensive coverage for Windows diagnostics, including registry health, system events, security risks, and component scans. A minor gap is the lack of tools for real-time monitoring or automated repair actions, but core diagnostic workflows are well-covered without dead ends.