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

    • you-design-mcp

      nuttawutkpi
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-aware clients to query and use the you-design catalog of design systems, skills, and plugins at runtime via stdio.
      -

    • inventory

      mcorona
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes three read-only tools over stdio — guarded SQL querying, SKU status lookup, and document retrieval — plus a schema resource. This lets MCP clients such as Claude Code answer stock and policy questions without any write access.
      MIT

    • gateway_lab.mcp_server

      adi0ri
      F
      license
      B
      quality
      C
      maintenance
      Provides a stdio MCP server with strict input validation and JSON-RPC error handling for tool calls.
      2
      -

    • openlane-mcp

      GregDog
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Cursor and Claude Desktop to query a GRC platform over stdio or HTTP, with read-only access by default and opt-in create, update, and delete tools subject to platform authorization.
      2
      Apache 2.0

    • Marketing Agent Eval Harness

      Praharsh-Projects
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides two MCP tools for querying a synthetic marketing SQLite database and running agent evaluation cases, with read-only SQL guarding and deterministic planning. The server communicates over stdio and supports initialization handshake and tool listing.
      -
    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

    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