Skip to main content
Glama
kmsmohamedansar

mcp-analytics-stub

by kmsmohamedansar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-analytics-stub

No user-submitted related servers found.

    Related Servers

    • ds-agent-mcp

      xiaomanwu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to delegate analytics questions, sample-size calculation, knowledge retrieval, and metric listing to a deterministic statistical engine over stdio JSON-RPC.
      MIT

    • io.github.edtool79

      edtool79-collab
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to run eight data tools over stdio for product search, ad transparency, company intent, job/ATS lookup, keyword volume, domain SEO, and YouTube transcripts, returning JSON envelopes with item limits, truncation metadata, and structured errors.
      386 PyPI
      MIT

    • OpsPilot MCP Server

      fferjani94
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only, deterministic tools for searching accounts and knowledge and retrieving tickets, ticket details, and product information over a stdio MCP connection.
      MIT

    • voice-agent-mcp

      irakli-ardia
      A
      license
      Not graded
      quality
      B
      maintenance
      Serves a single set of typed, validated tool definitions to MCP clients over stdio, letting them perform real actions through one controlled executor. The same definitions power a speech-driven OpenAI tool-calling agent, so voice and MCP clients share identical, validated capabilities.
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    resolve_category and get_insights target clearly different stages of the workflow (discovery vs. retrieval), and the descriptions explicitly explain the handoff via category ids. There is no overlap that could cause misselection.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun snake_case pattern. The convention is applied uniformly with no mixed styles or casing deviations.

    Tool Count3/5

    Two tools is thin but the stub scope (resolve a category, fetch its insights) is plausibly minimal. It sits at the borderline where an agent may need more surface for real work.

    Completeness3/5

    Coverage is a narrow two-step path: discovery requires a query string with no way to list all categories, and there is no pagination, time range, or drill-down beyond 'top insights'. Core workflow works but obvious gaps remain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources