Skip to main content
Glama
Swild000

hardened-ssh-mcp

by Swild000
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    With only one tool, there is no possibility of confusing it with another. The tool's purpose is singular and clearly described, leaving no ambiguity.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern (run-ssh-command), and with only one tool there are no inconsistencies to evaluate.

    Tool Count5/5

    One tool is exactly appropriate for a server whose sole purpose is to relay one command over SSH to a fixed host. Additional tools would be unnecessary and dilute the server's focus.

    Completeness5/5

    The tool covers all needed operations for its domain: it can preview a command without executing and execute with user confirmation. There are no obvious gaps for the stated purpose.

  • Average 4.8/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 3 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior5/5

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

    With no annotations, the description fully discloses behavioral constraints: fixed target, no access to other hosts or local filesystem, and a confirmation workflow that requires explicit per-turn consent. It even warns against assuming consent from an earlier command, which is valuable behavioral context.

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

    Conciseness4/5

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

    The description is somewhat lengthy but front-loaded with the core purpose. The 'Standing rule' segment clearly organizes usage guidance. Every sentence adds important information, though some repetition exists (e.g., 'nothing else' and 'only thing it can ever do').

    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?

    The description is comprehensive for a tool with no output schema and a fixed target: it covers capabilities, constraints, execution safety, and user consent protocol. It fully prepares an agent to use the tool correctly without needing additional external context.

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

    Parameters4/5

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

    Schema coverage is 100% so baseline is 3. The description adds meaningful nuance beyond the schema by explaining the confirmed parameter's workflow: preview with confirmed=false, execute only after user approval in the specific turn. This enhances understanding of how the parameters interplay.

    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 states the tool's exact function: 'Run exactly one command over SSH on the fixed target ubuntu@203.0.113.10 and nothing else.' It clearly defines the verb, resource, and scope, and explicitly distinguishes itself from hypothetical alternatives by noting it cannot reach other hosts or run local commands.

    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 provides an explicit standing rule: always show the user the exact command, get explicit go-ahead before calling, and use confirmed=false to preview. It also clarifies when not to use the tool (e.g., for local commands) by stating the tool cannot do those things.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

hardened-ssh-mcp MCP server

Copy to your README.md:

Score Badge

hardened-ssh-mcp MCP server

Copy to your README.md:

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/Swild000/hardened-ssh-mcp'

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