Cucumberstudio MCP Server

cucumberstudio-mcp npm v1.2.2 Source verified

Published by herosizy — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for Cucumber Studio API integration

Trust grade
A
100/100
Last scanned get badge →
Trust
A · 100/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 100/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 0 = 100. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

low Shell/command execution in packaging/dev tooling (scripts/npx-wrapper.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/npx-wrapper.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import { spawn } from 'child_process' import { join, dirname } from 'path' import { fileURLToPath } from 'url' // Get

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/npx-wrapper.js

low Shell/command execution in packaging/dev tooling (scripts/postinstall.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/postinstall.js:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: port { execSync } from 'child_process' // Get current directory for ES modules const __filename = fileURLToPath(import.

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/postinstall.js

low Shell/command execution in packaging/dev tooling (scripts/prepublish.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/prepublish.js:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: port { execSync } from 'child_process' // Get current directory for ES modules const __filename = fileURLToPath(import.

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/prepublish.js

Tools 15

Each tool and what it can reach — statically extracted from the published source.

  • cucumberstudio_configureno sensitive capability
  • cucumberstudio_find_action_words_by_tagsno sensitive capability
  • cucumberstudio_find_scenarios_by_tagsno sensitive capability
  • cucumberstudio_get_action_wordno sensitive capability
  • cucumberstudio_get_buildno sensitive capability
  • cucumberstudio_get_projectno sensitive capability
  • cucumberstudio_get_scenariono sensitive capability
  • cucumberstudio_get_test_executionsno sensitive capability
  • cucumberstudio_get_test_runno sensitive capability
  • cucumberstudio_list_action_wordsno sensitive capability
Show 5 more tools ↓
  • cucumberstudio_list_buildsno sensitive capability
  • cucumberstudio_list_execution_environmentsno sensitive capability
  • cucumberstudio_list_projectsno sensitive capability
  • cucumberstudio_list_scenariosno sensitive capability
  • cucumberstudio_list_test_runsno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.2.2 latest A 100/100 3 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/cucumberstudio-mcp/badge.svg)](https://mcptrustchecker.com/registry/cucumberstudio-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/cucumberstudio-mcp"><img src="https://mcptrustchecker.com/registry/cucumberstudio-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/cucumberstudio-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan cucumberstudio-mcp --online

Use the free API → How scoring works

More in Security & Testing