Skip to main content
Glama
aminamos

blazemeter-explorer

by aminamos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to blazemeter-explorer

No user-submitted related servers found.

    Related Servers

    • Frame.io V4 MCP

      yong6330
      F
      license
      A
      quality
      B
      maintenance
      Enables discovering and invoking all 97 published Frame.io V4 API operations through a searchable catalog, covering accounts, projects, folders, files, comments, shares, metadata, webhooks, and more using OAuth credentials. It also performs complete local multipart uploads, including chunked PUTs and upload status checks.
      5
      -
    • Britive MCP Server by britive

      Britive MCP Serverofficial

      britive
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents and users to interact with the Britive platform for dynamic access, query configurations, reporting, and access activity.
      1
      -

    • Buk MCP

      gmorande
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to explore and call the full documented API catalog, analyze salary history, payroll, team costs, and CPI comparisons, and optionally run isolated write operations.
      8
      MIT

    • SNC Cribl MCP

      atree1023
      A
      license
      A
      quality
      D
      maintenance
      Enables querying and exploring Cribl Stream and Edge deployments, providing access to worker groups, fleets, sources, destinations, pipelines, routes, event breakers, and lookups through a structured interface.
      7
      3
      MIT No Attribution
    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/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a distinct phase in the workflow: listing available operations, retrieving details for a specific operation, and invoking an operation. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: list_operations, get_operation, invoke_operation. This is predictable and easy to understand.

    Tool Count4/5

    With only 3 tools, the set is minimal but well-aligned with the server's purpose of exploring and invoking operations. It is on the lower end of the ideal range but not insufficient.

    Completeness5/5

    The tool set covers the complete lifecycle for its domain: discover operations (list), understand operations (get), and execute operations (invoke). No obvious gaps for the stated purpose of an explorer.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources