Skip to main content
Glama
sandraschi

glama-status-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to glama-status-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Tool Agent

      chigurupatiakhil5
      F
      license
      Not graded
      quality
      D
      maintenance
      A custom MCP server exposing database, ticketing, and external-API tools to both Claude Desktop and a self-built autonomous agent powered by Groq's free-tier LLaMA 3.3.
      -

    • dhl-ops-tools

      az-cod
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents and MCP clients to look up shipment tracking status, SAP order sync errors, ServiceNow incident tickets, and internal SOP runbooks through natural-language tool calls, with every execution written to a SQLite audit trail.
      -

    • whoop-ai-mcp

      thiagodegroot
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server that lets Claude Desktop, Claude Code, Codex and GitHub Copilot query WHOOP recovery, sleep, HRV, strain and workout data through natural language, answering questions about personal baselines, trends and sleep debt. It also rebuilds HYROX sessions, tracks triathlon load and readiness with auditable evidence, and serves a chart-first local dashboard.
      16 npm
      MIT
    • aegis-dq by aegis-dq

      aegis-dqofficial

      aegis-dq
      A
      license
      B
      quality
      D
      maintenance
      Agentic data quality MCP server — runs structured validation rules against warehouses (DuckDB, BigQuery, Athena, Databricks, Postgres), diagnoses failures with LLM root cause analysis, and proposes SQL remediations. Full audit trail of every AI decision.
      6
      4
      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

    A3.9/5.0

    Scored across 7 tools

    Disambiguation3/5

    Some overlap exists between dedicated report tools (glama_daily_report, glama_scores_summary) and the glama_status tool which has its own 'report' and 'list' operations. Descriptions try to clarify, but an agent might struggle to choose the correct tool for a given task.

    Naming Consistency5/5

    All tools follow a consistent 'glama_<descriptive_name>' pattern in snake_case, with clear verb_noun or descriptive names. There is no mixing of conventions or confusing styles.

    Tool Count5/5

    With 7 tools, the set is well-scoped for monitoring and analyzing Glama scores. Each tool has a distinct purpose, and the count feels neither too few nor too many.

    Completeness4/5

    The set covers analysis, reporting, summary, detailed queries, and rich cards. Missing a direct submission tool is acceptable as it's outside the server's scope. Minor gaps like lacking a bulk update feature are not critical.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources