Zephyr Scale MCP Server (Milo0821/Zephyr_mcp_server) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 18 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

Zephyr Scale MCP Server

An MCP server for Zephyr Scale test management supporting Jira Cloud and Data Center. It enables creating, reading, and managing test cases and test runs via the Atlassian REST API with official API-compliant schemas.

→ Milo0821/Zephyr_mcp_server· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Milo0821

Source: Glama · also listed on npm

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored herenpmscored separately

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: JIRA_API_TOKEN, ZEPHYR_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: JIRA_API_TOKEN, ZEPHYR_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretJIRA_API_TOKENNote: issue_links requires JIRA_USERNAME and to be set (Cloud only). Link failures are reported as warnings — the test case is still created.
configJIRA_TYPEForce "cloud" or "datacenter" — overrides auto-detection
configJIRA_USERNAMENote: issue_links requires and JIRA_API_TOKEN to be set (Cloud only). Link failures are reported as warnings — the test case is still created.
configZEPHYR_API_BASE_URLOverride the Zephyr API base URL (e.g. for EU: https://eu.api.zephyrscale.smartbear.com/v2). Defaults to US endpoint.
🔐 secretZEPHYR_API_KEYZephyr Scale API key (JWT). Generate in Jira: profile picture (bottom left) → Zephyr API keys
configZEPHYR_BASE_URLYour Jira Cloud URL, e.g. https://your-company.atlassian.net
// quality suggestions

All four hints declared on every tool

18/18 tools missing one or more hints — get_test_case (missing: destructiveHint, idempotentHint); create_test_case (missing: idempotentHint); update_test_case_bdd (missing: idempotentHint), +15 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 4/18 tools referenced in tests (22%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/milo0821/zephyr_mcp_server)](https://m8ven.ai/mcp/milo0821/zephyr_mcp_server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9b1c6ec8d873c2cef82bf90b86e562f0a8eef65f
code hash: 47396b0d4c2bcb6a8e9070352d624fef7ff539e959e23c7b5ab6f9280e8d9216
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client