Skip to main content
Glama
luisgf

infrabroker

by luisgf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Related Servers

Alternatives to infrabroker

No user-submitted related servers found.

    Related Servers

    • OpsPilot

      cswfww123
      A
      license
      B
      quality
      B
      maintenance
      Local AI ops broker that keeps SSH secrets on your machine, exposes intent-level MCP tools to agents, and requires approval via a loopback Web UI for dangerous writes.
      14
      1 npm
      MIT

    • brokre

      Furowu
      A
      license
      Not graded
      quality
      A
      maintenance
      Local credential broker that enables AI agents to securely run CLI tools like SSH and MySQL without exposing passwords to the AI context, environment variables, or process listings.
      3
      MIT

    • Charon

      NinadRao0707
      A
      license
      Not graded
      quality
      D
      maintenance
      Self-hostable control plane for managing the full lifecycle of non-human identities (AI agents), with short-lived credential issuance, attestation, and an MCP authorization gateway for per-tool access control.
      1
      MIT

    • SSH Vault MCP

      qsobad
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to securely access encrypted secrets (SSH keys, API tokens, passwords) with real-time user approval via Passkey, and supports SSH remote execution through the MCP protocol.
      -

    • Emisar

      AndrewDryga
      F
      license
      Not graded
      quality
      A
      maintenance
      Give AI agents Zero-Trust access to production infrastructure without the risks of granting them shell access. Actions are bounded by policy and an on-host runner.
      339
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct operation: single command execution, session-based execution, session lifecycle, file transfer, and host discovery. The descriptions explicitly guide tool selection, e.g., preferring ssh_execute for isolated commands and ssh_session_open for stateful sessions, leaving no ambiguity.

    Naming Consistency3/5

    Naming is mixed: ssh_get_file, ssh_put_file, and ssh_list_servers follow a verb_noun pattern, while ssh_session_open, ssh_session_exec, and ssh_session_close reverse the order to noun_verb. ssh_execute also lacks a noun. The prefix is consistent and readable, but the conventions are not uniform.

    Tool Count5/5

    Seven tools is ideal for an SSH broker: host discovery, single command execution, file transfer (get/put), and persistent session management (open/exec/close). Each tool serves a clear purpose without unnecessary overlap or bloat.

    Completeness5/5

    The surface covers the full remote-administration lifecycle: list hosts, run commands directly or via sessions, transfer files in both directions, and manage session resources. No critical operations are missing for the stated domain.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources