updated 2026-10-17 20:06 UTC

Cucumberstudio MCP

Repository

MCP Server for Cucumber Studio

MCP Servers TypeScript Listed MIT

Is Cucumberstudio MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.3 / 10
Provenance Attested
Signed commits 32%
Last push 203d ago
Advisories None known
Compare Cucumberstudio MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Cucumberstudio MCP scores 52.8/100 (Grade C), ranked #927 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.3/10; 32% of recent commits are signed; no published advisory affects its latest release (cucumberstudio-mcp); last pushed 2026-03-28. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cucumberstudio MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Cucumberstudio MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/HeroSizy/cucumberstudio-mcp, MIT, last pushed 2026-03-28. 32% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.3/10 (scanned Oct 13, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 3
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 3
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: cucumberstudio-mcp 1.2.2. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-11 OSSF Scorecard: 3.3/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Cucumberstudio MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Cucumberstudio MCP compares in MCP Servers

  1. #516 Akshare One MCP 52.9 +0.1
  2. #517 Figma MCP Rust 52.8 ±0
  3. #518 Cucumberstudio MCP 52.8 this agent
  4. #519 p6xer MCP Server 52.8 ±0
  5. #520 Joplin MCP Server 52.7 −0.1

Bars show each HVTrust score; the tick marks Cucumberstudio MCP’s 52.8.

Where the 52.8 comes from

HVTrust dimensions vs the MCP Servers average

52.8 / 100 · 100.0% confidence

Cucumberstudio MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.2 / 25
2.7 above avg 10.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
11.3 / 17
1.0 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.3 below avg 12.3
AdoptionLog-scaled stars · package downloads
5.3 / 20
2.1 below avg 7.4

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 24 spots (#861 → #885)
2026-09-26
Rank Moved
Rank rose 11 spots (#863 → #852)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.3/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 203 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Cucumberstudio MCP View MCP Servers Report missing data
12.4
Activity sub-score · out of 100
#518
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-17 20:06 UTC · Repo last pushed 203 days ago — may be stale

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
22
Forks
7
Last Push
2026-03-28
203 days ago
Commits (4 wk)
0
Downloads (7d)
33
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼5
was #922

Analysis

Activity Inputs

12.4 / 100
StarsRepository reach
8.2 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.2 / 20

Common questions about Cucumberstudio MCP

Public trust evidence for Cucumberstudio MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Cucumberstudio MCP publish package provenance?
Yes. Cucumberstudio MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Cucumberstudio MCP have an OpenSSF Scorecard?
Cucumberstudio MCP has an OpenSSF Scorecard score of 3.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Cucumberstudio MCP actively maintained?
Stale. The repository has not been pushed to in 203 days. Consider whether the project is still being maintained.
What license does Cucumberstudio MCP use?
Cucumberstudio MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cucumberstudio MCP's commits signed?
32% of the last 100 commits to Cucumberstudio MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Cucumberstudio MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Cucumberstudio MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Cucumberstudio MCP?

For maintainers

HVTrust scores Cucumberstudio MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 23HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1Provenance 1MCP 1
2026-10-09
Rank Moved
Rank dropped 24 spots (#861 → #885)
2026-09-26
Rank Moved
Rank rose 11 spots (#863 → #852)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 426 spots (#1281 → #855)
2026-09-23
HVTrust Changed
HVTrust up 38.8pts (14.0 → 52.8)
2026-09-22
Newly Listed
First tracked at rank #1281
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 16 spots (#835 → #851)
2026-09-12
Rank Moved
Rank dropped 10 spots (#814 → #824)
2026-09-11
Scorecard Added
OSSF Scorecard: 3.3/10
2026-09-11
Grade Changed
Trust grade D → C
2026-09-11
Rank Moved
Rank rose 176 spots (#990 → #814)
2026-09-11
HVTrust Changed
HVTrust up 6.9pts (46.7 → 53.6)
2026-09-09
Rank Moved
Rank dropped 15 spots (#975 → #990)
2026-09-08
Rank Moved
Rank dropped 10 spots (#965 → #975)
2026-09-07
Rank Moved
Rank dropped 50 spots (#915 → #965)
2026-09-06
Rank Moved
Rank dropped 14 spots (#901 → #915)
2026-09-05
Rank Moved
Rank dropped 54 spots (#847 → #901)
2026-09-04
Rank Moved
Rank dropped 35 spots (#812 → #847)
2026-09-03
Rank Moved
Rank dropped 47 spots (#765 → #812)
2026-09-02
Rank Moved
Rank rose 335 spots (#1100 → #765)
2026-09-02
HVTrust Changed
HVTrust up 16.0pts (31.9 → 47.9)
2026-09-01
Rank Moved
Rank dropped 42 spots (#1058 → #1100)
2026-08-31
Rank Moved
Rank dropped 32 spots (#1026 → #1058)
2026-08-30
Rank Moved
Rank dropped 56 spots (#970 → #1026)
2026-08-29
Rank Moved
Rank dropped 49 spots (#921 → #970)
2026-08-28
Rank Moved
Rank dropped 36 spots (#885 → #921)
2026-08-27
Rank Moved
Rank dropped 28 spots (#857 → #885)
2026-08-26
Rank Moved
Rank dropped 109 spots (#748 → #857)
2026-08-16
Rank Moved
Rank dropped 14 spots (#731 → #745)
2026-08-10
Rank Moved
Rank dropped 37 spots (#692 → #729)
2026-08-08
Newly Listed
First tracked at rank #691
GitHub → npm: cucumberstudio-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 52.8 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/cucumberstudio-mcp.svg)](https://hvtracker.net/agents/cucumberstudio-mcp)
HTML:
<a href="https://hvtracker.net/agents/cucumberstudio-mcp"><img src="https://hvtracker.net/badge/cucumberstudio-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON