mcp-server-computer
Provides an MCP server (stdio mode) that exposes a tool (queryConfig) to query local computer/system configuration: OS details, user information, Java runtime version, and platform-specific hardware/system info on Windows/macOS/Linux by executing relevant system commands.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security posture is largely unknown from the README. The server is described as stdio-mode MCP, likely intended for local/host-trusted use. It likely executes platform commands (systeminfo/system_profiler/lshw), which increases the risk surface if the execution environment is not tightly controlled. No authentication, authorization, or rate limiting is documented; ensure strict trust boundaries and command allowlisting/sandboxing. Dependency details and CVE status are not provided.
⚡ Reliability
Best When
Used as a local, controlled MCP tool in an environment where the agent is trusted and the host OS is known.
Avoid When
Avoid exposing this service to untrusted networks/users or multi-tenant contexts; avoid running on hosts where system command execution is tightly restricted.
Use Cases
- • Local environment discovery for AI agents (OS/user/Java version)
- • Generating machine capability summaries for automation workflows
- • Collecting basic diagnostics and compatibility info across platforms
- • Development-time checks for scripts/tools that need OS/hardware context
Not For
- • Remote administration or extracting sensitive host information for untrusted users
- • Highly security-sensitive environments where executing system commands is prohibited
- • Workloads requiring high reliability/error semantics across heterogeneous hosts without validation
Interface
Authentication
No authentication/authorization mechanism is described. The README indicates stdio mode for an MCP server, which typically relies on the surrounding host process for trust boundaries.
Pricing
No pricing information provided.
Agent Metadata
Known Gotchas
- ⚠ Platform command availability: Windows/macOS/Linux hardware queries depend on OS tools (systeminfo, system_profiler, lshw). Missing commands may cause failures.
- ⚠ Command execution/sandboxing: if the MCP runtime is sandboxed or restricted, tool calls may fail.
- ⚠ Output size/format consistency: system command outputs may vary by host and locale; agents should be robust to differences.
- ⚠ No documented auth/rate limiting: assume no protective limits beyond the host environment.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-computer.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.