A
licenseNot graded
qualityC
maintenanceEnables running YAML-defined test suites against MCP servers and agent workflows, with live or simulated execution, assertions, and regression reporting.
25 npm
MIT
Multimeter
by mshobeyri
Related Servers
Alternatives to Multimeter
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceCLI-first API testing tool with MCP server. Tests are .tarn.yaml; failures come back as structured JSON for AI agents to branch on. Tools: tarn_run, tarn_validate, tarn_fix_plan, tarn_inspect, tarn_rerun_failed.145MIT
- AlicenseBqualityCmaintenanceMCP server for generating, validating, running, and reporting Apache JMeter API performance tests from structured API sources.13700 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to discover API endpoints from OpenAPI/Swagger specs, send HTTP requests, validate responses, and analyze status codes for automated API testing.1-
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to execute Playwright-based UI and API test suites (login, inventory, checkout, API, regression) and receive structured JSON test results.0-
- AlicenseAqualityAmaintenanceEnables LLM clients to generate standardized test cases, perform quality control with lint scoring, convert to Xray/Jira format, and compose test suites (Smoke/Regression/E2E) with coverage analysis.92MIT
TDQS
A3.9/5.0
Scored across 9 tools
Disambiguation4/5
Most tools map to distinct workflow stages: learning syntax, seeing examples, discovering APIs, scaffolding, validating, formatting, and running. discover_api and api_card overlap for single-API inspection, but the descriptions make the preferred choice clear.
Naming Consistency4/5
Tool names mostly follow an imperative verb_noun pattern such as read_documentation, list_examples, discover_api, scaffold_test, validate, and run. api_card breaks the pattern as a noun-only name, but the inconsistency is minor and not confusing.
Tool Count5/5
Nine tools is well-scoped for this server's purpose of discovering, generating, validating, formatting, and running Multimeter tests. Each tool serves a clear role in the workflow without redundancy or bloat.
Completeness4/5
The toolset covers the core lifecycle from API discovery and test scaffolding to assertion suggestions, validation, formatting, and execution. A few peripheral capabilities like listing or deleting existing tests are absent, but agents can complete the primary authoring workflow without dead ends.
Maintenance
ActivityActive
ResponsivenessNo issues