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
      B
      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.
      -

    • ai-usage-mcp

      flaviozantut
      F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for querying AI usage metrics (exact tokens, cost, latency, errors, productivity) from a local SQLite database, enabling charts and analysis in Claude Code and Cursor.
      -

    • mcp-federated-data

      baller-coder
      A
      license
      Not graded
      quality
      D
      maintenance
      Federated MCP server that joins relational metadata (MySQL) with timeseries values (InfluxDB) behind a single, LLM-friendly entity layer.
      1
      MIT

    • MCPGate

      martin-santiago
      A
      license
      Not graded
      quality
      D
      maintenance
      MCPGate aggregates multiple MCP servers into a single unified endpoint, enabling centralized tool management with granular filtering, automatic namespacing, and observability. Features a real-time web dashboard and optional PostgreSQL-backed audit trails for monitoring and controlling AI tool access across local and remote deployments.
      6 npm
      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

    ActivityMaintained
    ResponsivenessNo issues

    Resources