Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BPMN Kit

NPM · @BPMNKIT/CLI

Create, validate, simulate and deploy Camunda 8 BPMN processes, forms and DMN from an agent.

Available components

npm · @bpmnkit/cli 47
0 this week 47 Trust /100

Last scanned (34 minutes ago)

Scores higher than 25% of npm servers

Category Workflow Automation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects nodemailer 6.10.1, reached via @bpmnkit/proxy > nodemailer. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 82 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to bpmnkit/bpmnkit). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • CVE-2026-121425 affects this package: high ▼ security
    • CVE-2026-121424 affects this package: high ▼ security
    • CVE-2026-121426 affects this package: high ▼ security
    • GHSA-85x2-q946-cp5h no longer affects this package ▲ security
    • GHSA-m943-m63m-w62w no longer affects this package ▲ security
    • GHSA-8c8m-p3m8-cjg8 no longer affects this package ▲ security
    • Dependency health: partial → 0.88 functional
  • 3 Nov 26 0
    • Dependency health: 0.88 → partial functional
  • 28 Oct 26 0
    • CVE-2026-110872 affects this package: high ▼ security
    • CVE-2026-110870 affects this package: high ▼ security
    • CVE-2026-110869 affects this package: high ▼ security
  • 24 Oct 26 0
    • GHSA-8c8m-p3m8-cjg8 affects this package: high ▼ security
    • GHSA-85x2-q946-cp5h affects this package: high ▼ security
    • GHSA-m943-m63m-w62w affects this package: high ▼ security
  • 23 Oct 26 0
    • CVE-2026-110871 affects this package: high ▼ security
  • 20 Oct 26 0
    • Package version: 1.3.1 → 1.4.0 functional
  • 14 Oct 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess. functional
  • 9 Oct 26 0
    • The attested source repository moved: bpmnkit/monorepo → bpmnkit/bpmnkit security
    • Package version: 1.3.0 → 1.3.1 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@bpmnkit/cli@1.4.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo bpmnkit/bpmnkit
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/bpmnkit/bpmnkit/.github/workflows/release.yml@refs/heads/main
Rekor log index 3338691193
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ac5d3a74afe044f45427cf169190997504d7c8363e77be3364a5afa65676d70c22155deeb80edd11f608dc8117592fd7d753cece49405d3eb6a972656

Background: How many MCP packages publish verified provenance →

Vulnerabilities 22 findings
ID CVE Severity Vector Fix available
GHSA-268h-hp4c-crq3 CVE-2026-82661 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N yes
GHSA-2x7j-588g-ccc2 CVE-2026-92596 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-39m8-27wv-hr27 CVE-2026-110871 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4ffr-jq9g-5ffx CVE-2026-110869 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4g23-2xm8-66gc CVE-2026-110872 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6vj9-mwq6-2f5v CVE-2026-100701 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-85x2-q946-cp5h CVE-2026-121426 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8c8m-p3m8-cjg8 CVE-2026-121424 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8m3c-c648-2xjj CVE-2026-92595 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8vvx-rff5-p5rq CVE-2026-100702 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-c7w3-x93f-qmm8 CVE-2026-82854 low yes
GHSA-cc9r-2j5m-2m83 CVE-2026-92597 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-g73g-hqqh-jr95 CVE-2026-110870 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-m943-m63m-w62w CVE-2026-121425 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-mm7p-fcc7-pg87 CVE-2025-13033 medium yes
GHSA-p6gq-j5cr-w38f CVE-2026-82659 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-r7g4-qg5f-qqm2 CVE-2026-82662 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-rcmh-qjqh-p98v CVE-2025-14874 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-v53p-9fqp-m79j CVE-2026-100700 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vvjj-xcjg-gr5g CVE-2026-82853 medium CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N yes
GHSA-wmmp-3585-3rmp CVE-2026-92598 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-wqvq-jvpq-h66f CVE-2026-82660 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 82 packages
Packages resolved 82
Deprecated 1
Stale 29
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the BPMN Kit MCP server?

BPMN Kit runs locally as an npm package, launched with npx -y @bpmnkit/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @bpmnkit/cli

# add to Claude Code
claude mcp add bpmnkit-bpmnkit -- npx -y @bpmnkit/cli
Common questions

What is the BPMN Kit MCP server?

BPMN Kit is an MCP server listed in the public MCP registry as io.github.bpmnkit/bpmnkit. Create, validate, simulate and deploy Camunda 8 BPMN processes, forms and DMN from an agent. This page covers its npm package (@bpmnkit/cli).

Is the BPMN Kit MCP server safe to use?

BPMN Kit scores 47 out of 100 on VerifyMCP. We recorded 22 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the BPMN Kit MCP server still maintained?

BPMN Kit is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the BPMN Kit MCP server under?

BPMN Kit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.