blazemeter-explorer
Related Servers
Alternatives to blazemeter-explorer
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables 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 Serverofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents and users to interact with the Britive platform for dynamic access, query configurations, reporting, and access activity.1-- AlicenseBqualityDmaintenanceExposes any GraphQL API as a single tool for executing queries and mutations with authentication support.1MIT
- AlicenseBqualityDmaintenanceEnables automated deployments, environment management, snapshots, and deployment monitoring through DevOps Deploy's REST API.157 npmMIT
- AlicenseAqualityDmaintenanceEnables 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.73MIT No Attribution
- FlicenseNot gradedqualityDmaintenanceEnables interaction with the Slingr platform, including application structure (Builder) and data management (Runtime), with documentation search and developer tools.-
TDQS
Scored across 3 tools
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.
All tool names follow a consistent verb_noun snake_case pattern: list_operations, get_operation, invoke_operation. This is predictable and easy to understand.
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.
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.