Skip to main content
Glama
Sign In
Tusk Drift MCP

Tusk Drift MCP

by Use-Tusk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Tusk Drift MCP

No user-submitted related servers found.

    Related Servers

    • reqlog

      ankitksr
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding agents with tools to query, search, and analyze persisted HTTP request logs, enabling efficient debugging without terminal noise.
      MIT

    • tracehub-mcp

      mcpsmiths
      A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to OpenTelemetry trace backends (Jaeger, Grafana Tempo, Traceloop, Datadog, Sentry, AWS X-Ray, New Relic and Honeycomb) for natural-language trace and span search, error triage, cross-backend correlation, and LLM analytics such as token usage, model performance and the most expensive or slowest traces.
      19
      169 PyPI
      1
      Apache 2.0
    • @originchain/telemetry-mcp

      @originchain/telemetry-mcpofficial

      originchain-ai
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to query OriginChain's telemetry agent for log patterns, semantic incident analysis, distributed traces, service graphs, and read-only SQL queries over telemetry data.
      10
      4 npm
      MIT

    • otel-pocket

      kanchingyg
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a local OTLP trace collector: list recent traces, inspect span trees and critical paths, flag SQL N+1 loops, surface gen_ai metrics, and diagnose slow traces with a local OpenAI-compatible model.
      MIT
    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.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool serves a clear, distinct purpose: aggregation, schema discovery, span detail retrieval, trace tree, field value exploration, and search. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores (e.g., aggregate_spans, list_distinct_values, query_spans). No mixing of styles.

    Tool Count5/5

    6 tools is well-scoped for a telemetry/observability server, covering all necessary operations without being overwhelming or too sparse.

    Completeness5/5

    The tool set covers querying, aggregation, trace retrieval, span details, schema exploration, and field value discovery. No obvious gaps for the domain of analyzing API traffic spans.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources