D

npm:mcp-zebrunner

https://www.npmjs.com/package/mcp-zebrunner
65/100 · MCP Trust Grade · checked 2h ago · MCP 5.16.1

What it offers — 29 tools · Developer Tools

list_test_suites

📋 List test suites for a project (✅ Verified Working)

get_test_suite

Legacy: Return detailed info of a test suite by suite_id (Limited availability)

list_test_cases

Legacy: Return list of test cases for a given test suite (Limited availability)

get_test_case

Legacy: Return detailed info of a test case by case_id

get_test_case_by_key

🔍 Get detailed test case by key (✅ Verified Working)

search_test_cases

Search test cases by query (requires project_key or project_id, supports pagination: page, size)

get_test_cases

📋 Retrieve test cases from Zebrunner with advanced filtering and pagination

find_test_case_by_key

🔍 Find a specific test case by its key with detailed information

get_test_suites

📂 Retrieve test suites from Zebrunner with pagination support

get_suite_hierarchy

🌳 Get hierarchical view of test suites with depth control

get_root_suites

Get only root-level test suites with hierarchy information

get_test_runs

Retrieve test execution runs with filtering by status, milestone, build, etc.

get_test_results

Get test results for a specific test run

get_test_cases_by_suite

Get all test cases belonging to a specific test suite

get_test_cases_enhanced

Retrieve test cases with advanced filtering, pagination, and multiple output formats

get_test_suites_enhanced

Retrieve test suites with hierarchy support and multiple output formats

find_test_case_by_key_enhanced

Find a specific test case by its key with enhanced formatting and multiple output formats

get_all_subsuites

📋 Get all subsuites from a root suite as flat list with pagination

+11 more tools

Spec / packaging20%85
Security (OWASP MCP)30%25
Maintenance / popularity20%83
Tool hygiene15%70
Transparency / provenance15%90

Findings

WARNMCP08 References sensitive file paths / environment secrets.
INFO Static analysis of npm package mcp-zebrunner@5.16.1 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:mcp-zebrunner on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:mcp-zebrunner grade D
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade D · wmcp.sh
[![MCP Trust Grade D](https://wmcp.sh/mcp/grade/npm%3Amcp-zebrunner/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Amcp-zebrunner)
<a href="https://wmcp.sh/mcp/grade/npm%3Amcp-zebrunner"><img src="https://wmcp.sh/mcp/grade/npm%3Amcp-zebrunner/badge.svg" alt="MCP Trust Grade D · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.