Skip to main content
Glama
Sign In
paarthureddy

Protocol-0

by paarthureddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin

Related Servers

Alternatives to Protocol-0

No user-submitted related servers found.

    Related Servers

    • SentinelMCP

      AnanthanarayanKV
      F
      license
      A
      quality
      D
      maintenance
      Enables LLM-driven agents to autonomously detect, diagnose, repair, verify, and prevent software and hardware failures on local and remote systems. Includes built-in safety checks and automatic rollbacks.
      15
      -

    • Cairn

      Nouman-Amjad
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to investigate infrastructure incidents in plain English, correlate observability and deploy data with runbooks, and get evidence-backed root-cause proposals with approval-gated remediation.
      5
      -

    • MCP SSH Orchestrator

      samerfarida
      A
      license
      B
      quality
      A
      maintenance
      Provides policy-driven, auditable SSH access to server fleets for AI assistants with zero-trust security controls, command whitelisting, and comprehensive audit logging to safely manage infrastructure.
      13
      28
      Apache 2.0

    • AI Incident Monitoring RCA MCP

      lokeshkundi15
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides telemetry tools for retrieving recent logs and system metrics to support root-cause analysis of infrastructure incidents. Enables autonomous incident triage with grounded verification and human-in-the-loop remediation.
      1
      -

    • Governed MCP Gateway

      marlyngiselle
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to safely interact with operations systems such as cloud inventory, runbooks, and ticketing while enforcing role-based access, JWT authentication, write confirmation, secret and PII redaction, rate limits, and audit logging.
      MIT
    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

    C2.8/5.0

    Scored across 20 tools

    Disambiguation3/5

    Most tools have distinct purposes, but there are three legacy alias pairs (get_incident/getIncidentReport, get_company_health/getCompanyHealth, get_agent_activity/getAgentActivity) that create direct overlap, causing potential confusion for an agent.

    Naming Consistency2/5

    The toolset mixes camelCase (e.g., triggerIncident, startMonitoring) and snake_case (e.g., simulate_disaster, list_incidents) inconsistently, with no clear pattern or rationale for the variation.

    Tool Count3/5

    20 tools is on the higher side for a typical server, but the broad scope (simulation, monitoring, incident management, actions) could justify it, though the presence of three duplicate aliases makes the count feel slightly bloated.

    Completeness4/5

    The toolset covers a wide range of incident and monitoring operations: simulation, monitoring, security, health reports, incident details, recommendations, and approvals. Minor gaps exist (e.g., no manual incident creation or update), but the surface is largely sufficient for its domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources