Skip to main content
Glama
Sign In
vps-ops-mcp

vps-ops-mcp

by Akdag94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Security audit

security_audit

Audit a remote server's security: inspect listening ports, firewall rules, fail2ban jails, SSH hardening, pending updates, and recent logins. Checks requiring sudo degrade gracefully.

Instructions

Read-only security posture check: listening ports, UFW firewall rules, fail2ban jails, sshd hardening flags (root login / password auth), pending security updates, recent logins. Sub-checks that need passwordless sudo degrade gracefully with a note.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>"
    },
    "name": "security_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesSSH host alias from ~/.ssh/config, or user@hostname

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses that the operation is read-only and that sub-checks requiring passwordless sudo will 'degrade gracefully with a note'. This adds valuable behavioral context beyond the input schema, especially since no annotations are provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences, no extraneous information, and front-loads the purpose. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one parameter and no output schema, the description covers the main functionality and important behavior (degradation). It lists the checks performed, which helps an agent infer output structure. Slightly less complete if the output format is needed, but adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already fully describes the single 'host' parameter with its format. The description does not add additional semantic meaning beyond this, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is a 'Read-only security posture check' and enumerates specific areas checked (listening ports, UFW, fail2ban, sshd, updates, logins), making its purpose unambiguous and distinct from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for security checks but does not explicitly state when to use this tool versus alternatives like server_health or ssl_status. It mentions graceful degradation for missing sudo, which gives some context but lacks clear when-to-use / when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools