Skip to main content
Glama
isp-analytics-mcp

isp-analytics-mcp

by KaiqueSavi

Related Servers

Alternatives to isp-analytics-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query internal business data for insights into customers, revenue, subscriptions, sales, and churn through controlled, read-only MCP tools.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to explore a synthetic product-event dataset and answer questions about signups, trends, funnels, and property breakdowns using a small set of composable, self-describing tools that return precomputed totals and actionable error hints.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables an AI assistant to answer customer-success questions by synthesizing simulated billing, support ticket, and product usage data into composite churn-risk scores, bands, and plain-language explanations for fictional accounts. It exposes raw-data tools, a synthesis tool, and a methodology resource so users can list at-risk accounts or get a per-account health summary.
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to discover and execute analytical queries on a DuckDB dataset through typed MCP tools, with guarded read-only SQL support for complex calculations without direct database access.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query onchain app analytics and attribution, including visitors, wallets, transactions, revenue, funnels, retention, and traffic sources, and to manage boards, charts, segments, alerts, and wallet labels through natural language.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with operational customer context, including typed revenue objects, persistent state, scoped tools, and human-in-the-loop handoffs through MCP, REST, and CLI.
      15 npm
      13
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation4/5

    The tools mostly target clearly distinct analytical angles: the churn family splits cleanly into trend (by_month), reasons, segment breakdown, and risk scoring, and the delinquency family into aging buckets, due-month flow, and customer list. Minor overlap exists between ticket_stats and tickets_by_month, since the latter covers a time dimension that arguably belongs in the former, and overview partially duplicates churn/delinquency KPIs at a single snapshot.

    Naming Consistency4/5

    Nearly all tools follow a consistent snake_case `<domain>_<qualifier>` pattern (churn_by_month, churn_reasons, delinquency_aging, ticket_stats), which makes the set predictable. The outliers are the bare `overview` and the verb-first `run_sql`, but they are few and their roles are self-evident.

    Tool Count5/5

    13 tools sits comfortably in the well-scoped range, and each one maps to a concrete analytical question (churn, delinquency, retention, sales, tickets). No padding is visible, and run_sql acts as a deliberate escape hatch rather than bloat.

    Completeness4/5

    The surface covers the core ISP analytics lifecycle: KPIs, churn in four dimensions, delinquency in three, cohort retention, sales acquisition, and support tickets, plus a read-only SQL fallback. The main gap is revenue evolution over time — sales_by_month reports only new MRR, with no total MRR/ARPU trend or expansion/contraction view, though run_sql can backfill this.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues