corporate-mcp-system-inspector
Related Servers
Alternatives to corporate-mcp-system-inspector
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables read-only observability of a Linux host via MCP, exposing allowlisted systemd, docker, nginx, logs, disk, and cert info without shell access.MIT
- AlicenseBqualityBmaintenanceEnables read-only inspection of local Windows and Linux systems for host, resource, network, service, software, identity, startup, certificate, SSH key metadata, and environment-variable name evidence through MCP tools. It normalizes platform outputs into stable schemas while avoiding arbitrary shell execution, credential reads, secret values, or remediation.23MIT
- AlicenseAqualityCmaintenanceEnables read-only Kubernetes cluster inspection through MCP, with namespace allow/deny and resource block policies enforced before any API call.11Apache 2.0
- AlicenseAqualityBmaintenanceEnables local, offline inspection of computer activity by collecting visible process, connection, and automatic-launch metadata and letting MCP clients explain rule matches and process context. It is read-only toward processes and system settings and offers review suggestions without making changes.8MIT
- AlicenseAqualityCmaintenanceEnables MCP clients on macOS to perform bounded read-only filesystem operations and a narrow allowlist of process diagnostics over STDIO or authenticated loopback Streamable HTTP. It excludes file writes, arbitrary shell access, GUI/browser automation, and remote relay.10MIT
- AlicenseAqualityDmaintenanceProvides read-only access to host system metrics (CPU, memory, disk), Docker container health/logs, and sandboxed log file analysis via MCP tools, enabling AI agents to monitor enterprise infrastructure safely.3MIT
TDQS
Scored across 4 tools
Each tool targets a clearly separate subsystem: identity, resources, processes, and network. There is no functional overlap or ambiguity between the tool names and their stated purposes.
Tool names follow a readable noun-based pattern, with system_ prefix used for two tools and _summary suffix used for the other two. While not perfectly uniform, the naming is predictable and easy to reason about.
Four tools is a well-scoped count for a system inspection server. Each tool covers a distinct high-level concern without unnecessary fragmentation or redundancy.
The surface covers the core system inspection areas: identity, resources, processes, and network. Minor gaps such as detailed disk I/O or user/session information exist, but they are not essential for basic system inspection.