Skip to main content
Glama
argosvix

@argosvix/mcp-server

by argosvix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @argosvix/mcp-server

No user-submitted related servers found.

    Related Servers

    • Production Monitoring MCP

      kowshik3383
      F
      license
      A
      quality
      B
      maintenance
      Connects AI agents to live observability stacks including Sentry, GitHub, Vercel, Better Stack, and Cloudflare, enabling end-to-end incident investigation, deployment correlation, root cause analysis, and regression triage.
      14
      -

    • codinfy-agent-monitor

      bakalagoin
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides real-time monitoring of AI agents, context, usage limits, workflows, files, Git, tests, builds, errors, secrets, and model-economy advice for tools like Claude Code, Codex, and Cursor, with 30 MCP tools for comprehensive observability.
      1
      -
    • Warpmetrics MCP Server by warpmetrics

      Warpmetrics MCP Serverofficial

      warpmetrics
      A
      license
      A
      quality
      C
      maintenance
      Connects AI assistants to Warpmetrics telemetry data to monitor AI agent performance, execution runs, and LLM costs. It allows users to query success rates, latency, and spend metrics directly through natural language interfaces.
      20
      37 npm
      MIT

    • k8s-telemetry-mcp

      kubeopsai
      A
      license
      A
      quality
      B
      maintenance
      Gives AI assistants read-only access to a Kubernetes cluster's observability stack — Loki, Prometheus, Tempo, the Kubernetes API — plus AWS telemetry from CloudTrail, Config, ECR, and RDS. 23 tools for querying logs, metrics, traces, Kubernetes events, deployments, and audit history in plain language.
      23
      Apache 2.0
    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 87 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose. For example, there are multiple alert-related tools (acknowledge_alert, auto_silence_noisy_alert, silence_alert, etc.) but each targets a unique action like acknowledging a single event, bulk-silencing, or muting. Descriptions are detailed enough to avoid ambiguity.

    Naming Consistency5/5

    All 87 tool names follow a consistent verb_noun pattern in snake_case (e.g., create_alert, list_alerts, delete_alert). Verbs like get, list, create, update, delete, propose, etc. are used uniformly, making naming predictable.

    Tool Count3/5

    With 87 tools, the count is very high and exceeds typical well-scoped ranges (3-15). However, the server covers a broad domain (calls, alerts, budgets, evaluations, prompts, projects, etc.) as a comprehensive admin interface, so the count is somewhat justified but still feels heavy.

    Completeness5/5

    The tool set covers core CRUD/lifecycle operations for each subdomain (alerts, calls, eval, prompts, webhooks, budgets, policies, projects). There are no obvious gaps; even advanced operations like automated silencing, proposal reply, and approval request are included.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources