Skip to main content
Glama
itoc360

ITOC360 MCP Server

Official
by itoc360
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ITOC360 MCP Server

No user-submitted related servers found.

    Related Servers

    • PilotOps MCP

      muhammedehab35
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-driven incident response by connecting Claude to monitoring tools like Prometheus, Grafana, Loki, PagerDuty, and Slack for automated investigation and runbook generation.
      9
      -

    • PagerDuty MCP Server

      dinesh-it
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with PagerDuty services, incidents, schedules, and on-call management through natural language.
      -

    • 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
      -

    • Faultline

      aawhan0
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP-native AI incident response system that empowers agents to investigate production incidents, collect evidence, hypothesize root causes, and drive controlled remediation and recovery verification.
      1
      -
    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.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    send_alert and resolve_alert are mutually exclusive lifecycle actions with no semantic overlap. An agent cannot confuse raising an alert with resolving one.

    Naming Consistency5/5

    Both tools follow the same verb_noun pattern: send_alert and resolve_alert. The naming is perfectly consistent and predictable.

    Tool Count3/5

    At only two tools, the server is on the thin side, but the narrow alerting domain justifies a minimal surface. It feels borderline rather than fully well-scoped.

    Completeness4/5

    The core send/resolve alert lifecycle is covered, including update semantics via fingerprint reuse. However, there is no way to list or inspect alert status, which is a minor gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources