Skip to main content
Glama
razornne

metrics-mcp

by razornne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to metrics-mcp

No user-submitted related servers found.

    Related Servers

    • governed-analytics-agent

      Binary-yev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to answer analytics questions with provable correctness by resolving metrics through the semantic layer, tracing lineage, traversing knowledge graphs, checking freshness, and searching glossary definitions, while enforcing access controls and logging every call.
      MIT

    • horizon-mcp-demo

      christianashworth
      F
      license
      Not graded
      quality
      B
      maintenance
      Exposes a governed semantic layer built on dbt Core and DuckDB, enabling AI agents to query predefined metric definitions for a P&C insurance dataset. Prevents metric hallucination by restricting agents to governed tools and read-only data access.
      -

    • SLayer

      MotleyAI
      A
      license
      A
      quality
      A
      maintenance
      Agent-native semantic layer, letting AI agents query databases through specifying intent instead of writing SQL, then compiling structured queries into correct, dialect-aware SQL. Dynamic and expressive, supporting multi-stage queries, time-shifts, and complex join schemas.
      20
      364 PyPI
      221
      MIT
    • dst by get-dst

      dstofficial

      get-dst
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to query governed data warehouses through plain language, returning grounded answers with SQL, confidence grades, and signed receipts while enforcing access, testing, and audit controls.
      12
      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 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: listing available metrics, retrieving full definitions with caveats, computing metric values, and verifying drafted answers. There is no overlap or ambiguity about which tool to call for a given step.

    Naming Consistency5/5

    All tool names follow the same snake_case verb_noun pattern: list_metrics, get_metric, query_metric, verify_answer. The pattern is consistent and predictable, with only the expected singular/plural variation for the metric resource.

    Tool Count5/5

    Four tools is well-scoped for a read-only metrics warehouse surface. Each tool covers a necessary step in the workflow and none feel redundant or missing.

    Completeness5/5

    The tool set covers the full analytical workflow: discover what metrics exist, understand their exact definitions and caveats, query them, and verify any final answer before it is delivered. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources