Skip to main content
Glama
alexcgodwin

OpsChugex LocalOps MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
system_infoB

Return bounded operating-system and host metadata using Node.js system APIs.

system_healthA

Summarize CPU, memory and fixed-disk pressure without changing the host.

cpu_statusC

Sample CPU utilization and return processor metadata and load averages.

memory_statusA

Return total, used and available physical memory.

disk_statusA

Inspect fixed local disk capacity and utilization using a bounded platform-specific command.

network_interfacesA

List local network interfaces and assigned addresses. No network probing is performed.

list_processesA

List a bounded number of local processes with basic resource metadata. Command lines and environment variables are not returned.

inspect_processA

Inspect one local process by numeric PID without returning its environment or command-line arguments.

list_servicesA

List a bounded number of Windows services or systemd services and their states.

service_statusA

Inspect one Windows or systemd service. Service names are strictly validated before use.

uptimeA

Return system uptime in seconds, hours and days.

installed_softwareA

Return a bounded installed-software inventory with versions and publisher metadata. Windows reads uninstall registry metadata; Linux uses the available package database.

software_versionsA

Look up installed versions for up to 50 requested software names without launching or modifying the software.

software_changesA

Compare the current bounded installed-software inventory with a caller-supplied baseline. The server does not persist a baseline or write to disk.

local_usersB

Return bounded local account metadata. Passwords, password hashes and credential material are never returned.

local_groupsB

Return bounded local group metadata and Linux group membership where available.

local_adminsA

Identify members of the built-in Windows Administrators group or common Linux administrative groups without modifying membership.

startup_programsA

Inventory Windows startup registrations or enabled Linux systemd/XDG startup entries. Startup command lines are intentionally not returned.

scheduled_tasksA

Inventory Windows scheduled tasks or Linux systemd timers and cron directory entries without returning task action commands.

certificate_inventoryA

Inventory bounded certificate metadata and expiry dates. Private key material is never read or returned.

certificate_expiryB

Return certificates already expired or expiring within the requested window.

ssh_key_inventoryA

List metadata for files in the current user's SSH directory. Key contents, private key material and authorized key contents are never read or returned.

environment_variables_summaryB

Return environment-variable names and a sensitive-name flag only. Values are never exposed.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 23 tools

Disambiguation4/5

Most tools target distinct resources or actions, but the system health area has some overlap: system_health summarizes CPU, memory, and disk while cpu_status, memory_status, and disk_status provide detailed views of the same domains. Descriptions help distinguish them, but an agent could still hesitate between a summary tool and a detail tool.

Naming Consistency4/5

All names use snake_case, which is consistent, but the conventions vary between noun phrases (system_info, cpu_status, network_interfaces) and verb-led names (list_processes, inspect_process, list_services). The pattern is readable but not uniform verb_noun throughout.

Tool Count3/5

23 tools sits in the 16-25 range that the rubric calls borderline heavy for a server's scope. While many tools serve distinct read-only inspection needs, several could be consolidated with the summary tools, making the surface feel somewhat expansive.

Completeness4/5

Coverage is broad for local read-only system inspection: hardware, OS, processes, services, software, users, security artifacts, startup, and scheduled tasks are all represented. Minor gaps exist, such as network connection/port inspection and event log access, but agents can work around most of these.

Maintenance

ActivityMaintained
ResponsivenessNo issues