Skip to main content
Glama
hypnosis

SSH MCP Server

by hypnosis
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

ssh_audit_baseline

Read-only

Audit a machine's setup in one SSH round trip, reporting sshd, firewall, updates, services, docker, ports, and disk with CRITICAL, WARNING, or OK status.

Instructions

Reports how a machine is set up: sshd, firewall, pending updates, failed services, docker, listening ports and disk, each section marked CRITICAL, WARNING or OK. Reads only, in one round trip instead of a dozen commands. For load and health at this moment rather than settings, use ssh_snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
compactNoTrim the long sections. false = whole, much larger answer. Default: true
includeNosystem, disk, mem, net, ssh, services, docker, firewall, updates. Default: all
profileYesMachine name.
include_sudo_sectionsNoRun the sections that need root as root: sshd -T for ssh, ufw and iptables rules for firewall. Without it those sections name what they could not read instead of guessing. Default: false

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
osNo
netNo
sshNo
diskNo
loadNo
dockerNo
kernelNo
legendNoWhat the words in this answer mean. A key names the field before the value — "state=limited", "jobs[].state=lost" — and only the values this answer actually used are listed.
memoryNo
uptimeNo
updatesNo
date_utcNo
firewallNo
hostnameNo
servicesNo
red_flagsNo
unavailableNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv2.3.3
    • changedInput schema / properties / include_sudo_sections / description
      Previous value: -"Read sshd config as sshd sees it (sshd -T), needs root. Without it the ssh section says so instead of guessing from the file. Default: false"New value: +"Run the sections that need root as root: sshd -T for ssh, ufw and iptables rules for firewall. Without it those sections name what they could not read instead of guessing. Default: false"
    • addedOutput schema / properties / firewall / properties / iptables / properties / status / description
      Added value: +"not_installed — the tool is absent from the server, so it filters nothing here; no_access — the tool is there, but reading its rules needs root: what it allows is unknown; read — the rules were read, and the fields beside this one come from them."
    • addedOutput schema / properties / firewall / properties / ufw / properties / status / description
      Added value: +"not_installed — the tool is absent from the server, so it filters nothing here; no_access — the tool is there, but reading its rules needs root: what it allows is unknown; read — the rules were read, and the fields beside this one come from them."
    • addedOutput schema / properties / legend
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "What the words in this answer mean. A key names the field before the value — \"state=limited\", \"jobs[].state=lost\" — and only the values this answer actually used are listed.",
+  "type": "object"
+}
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotation already declares readOnlyHint=true, and the description reinforces this with 'Reads only'. It adds useful behavioral context beyond the annotation by stating that sections are marked CRITICAL/WARNING/OK and that it replaces 'a dozen commands' in one round trip. No contradiction with annotations.

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?

Three sentences with no filler: the first defines purpose and output shape, the second states safety and efficiency, and the third routes to the sibling tool. The most important scoping information is front-loaded.

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

Completeness5/5

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

For a read-only audit tool, the description covers what it reports, how the output is categorized, why it is efficient, and which sibling to use in the alternate use case. Combined with full parameter documentation and an output schema, nothing essential is missing.

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?

Schema description coverage is 100%, with every parameter documented including defaults and allowed values. The tool description contributes high-level context but does not need to compensate for missing parameter docs, so the baseline 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 opens with a specific verb and resource: 'Reports how a machine is set up', then enumerates exact domains (sshd, firewall, updates, services, docker, ports, disk) and the severity marking scheme. It also distinguishes itself from ssh_snapshot, so an agent can tell it apart from the closest sibling.

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

Usage Guidelines5/5

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

The description gives explicit routing guidance: 'For load and health at this moment rather than settings, use ssh_snapshot.' It also frames the tool as a one-round-trip setup audit, making the intended use case clear without ambiguity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hypnosis/ssh-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server