io.github.vilaabo/zephyr-scale-mcp
io.github.vilaabo/zephyr-scale-mcp
Is the io.github.vilaabo/zephyr-scale-mcp MCP server down? No. It is up and needs env, probed 2026-10-27.
Zephyr Scale on self-hosted Jira Server/DC: test cases, cycles, executions, plans and attachments
needs env probed 2026-11-15 · unchanged since 2026-10-27
MCP error -32000: Connection closed - JIRA_TLS_REJECT_UNAUTHORIZED must be 'true' or 'false', got 'mcpcost-placeholder' - ZEPHYR_READONLY must be 'true' or 'fal
- Run it
- npx -y zephyr-scale-mcp@1.0.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/vilaabo/zephyr-scale-mcp
- Registry
- active, updated 2026-07-31 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Invoice Studio io.github.vijayst/invoice-studio · alive
- Aletheia Runtime Safety & Scope Creep Filter io.github.vikasny30/aletheia-mcp · alive
- Switzerland MCP 🇨🇭 io.github.vikramgorla/swiss · alive
- io.github.viktorlarsson/openfigi · alive
- io.github.vince-gonzalez/colorblind · alive
- io.github.vince-gonzalez/cvdsafe · alive
- Devloop io.github.vincentvella/devloop · alive
- io.github.vineethwilson15/semamerge · alive
Servers that mention zephyr or attachments or executions.
- io.github.jmshinhwa/firmware-release-gate · alive
- Eclipse Zephyr MCP io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/zephyr · not probed
- Familia com.familiaplanner/familia · alive
- com.formester/mcp · needs auth
- SotoGoal com.sotogoal/sotogoal · needs auth
- dev.mailkite/mail-send · needs auth
- Email Inbox API + Sending by Sendmux io.github.Sendmux/sendmux-mcp · needs auth
- io.github.kubeshop/testkube-mcp · needs your URL
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server exits because an environment variable is missing. The probe starts the package without secrets. A server that starts without secrets and asks for them on the first tool call is measured.