Is bzm-mcp safe to use?

bzm-mcp scores 92/100 (grade A) on the Canopii Trust Index — strong posture. It passes 16 of the 20 security controls that apply to it, with no confirmed security failures.

How reliable is the security score for bzm-mcp?

We could evaluate 98% of the controls that apply to bzm-mcp. Scores are deterministic — the same source always produces the same score — and a partially-scannable server cannot present a high one, because confidence caps the result. The scanner is open source, so this score can be reproduced independently.

How was bzm-mcp scored?

Its published source was scanned against a fixed catalog of weighted security controls covering code safety, committed secrets, dependency vulnerabilities, tool-description integrity, authentication and transport, and maintenance. A confirmed flaw caps the score outright regardless of what else passes. The full rubric is published.

bzm-mcp MCP Server Security Report

Blazemeter/bzm-mcp

Official BlazeMeter MCP Server for AI-driven performance testing

92A

Security Trust Score

Grade A · Strong posture

Tier 1 · Public sourceHigh confidence · 98%latest vmain@6a43033 Repository

Declared MCP capabilities

Prompts

Run it securely

Host Blazemeter/bzm-mcp in a governed environment — SSO in front, every tool call attributed and audited.

Are you the maintainer?

Verify with GitHub to get alerted whenever Blazemeter/bzm-mcp changes score — and claim the badge for your README.

Claim this server

The short answer

Is bzm-mcp safe to use?: bzm-mcp scores 92/100 (grade A) on the Canopii Trust Index — strong posture. It passes 16 of the 20 security controls that apply to it, with no confirmed security failures.
How reliable is the security score for bzm-mcp?: We could evaluate 98% of the controls that apply to bzm-mcp. Scores are deterministic — the same source always produces the same score — and a partially-scannable server cannot present a high one, because confidence caps the result. The scanner is open source, so this score can be reproduced independently.
How was bzm-mcp scored?: Its published source was scanned against a fixed catalog of weighted security controls covering code safety, committed secrets, dependency vulnerabilities, tool-description integrity, authentication and transport, and maintenance. A confirmed flaw caps the score outright regardless of what else passes. The full rubric is published.

Reputation26stars7forks13open issues3d agolast commit<1yage

Security controlslatest scored version vmain@6a43033

Each control is evaluated deterministically with evidence. The score is earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

Warn
Strict JSON Schema Enforcementschemas not strict
Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.
Fix: Set additionalProperties:false and require explicit parameters on every tool.
Pass
Indirect Prompt Injection (IPI) Defensesguardno injection markers
Tool/prompt/resource text is free of hidden instructions that could hijack the agent.
Pass
User-in-the-Loop / Approval Scopeguardno destructive tool scope
No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.
N/A
Tool Definition Integrityguardno prior version to diff
Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

Application Security Checks

Warn
No known-vulnerable dependencies10 of 68 runtime deps vulnerable; worst high
Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.
[email protected] — PYSEC-2026-2132[email protected] — GHSA-537c-gmf6-5ccf[email protected] — GHSA-g6cj-pr64-35w5[email protected] — GHSA-jwv3-5hgf-82ww
Fix: Upgrade the flagged dependencies past their fixed versions.
Pass
No command-injection sinksguardno sinks found
Untrusted tool input reaching a shell yields remote code execution.
Pass
No dynamic code executionguardno sinks found
eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.
Pass
No path traversalguardno sinks found
Naive path checks let tools read/write outside intended directories (EscapeRoute-class).
Pass
No SSRF sinksguardno sinks found
Fetching tool-supplied URLs can pivot into internal networks and metadata services.
Pass
No unsafe deserializationguardno sinks found
pickle/yaml.load/etc. on untrusted data can execute code.
Pass
No committed secretsguardno secrets found
Hardcoded keys/tokens in published source are live credentials an attacker can use.
Pass
Credentials sourced from environmentreads credentials from environment
Reading secrets from env/secret stores avoids hardcoding them.
Pass
Dependencies pinned (lockfile)lockfile present
A lockfile makes installs reproducible and resistant to silent dependency swaps.
Pass
Actively maintainedrecent commits
Unmaintained servers don't receive security fixes.
Pass
Repository not archivedguardactive
Archived repositories will never be patched.
Pass
Declares a licenseApache-2.0
A clear license is required for legal enterprise use.
Pass
Has a security policySECURITY.md present
A SECURITY.md gives a private path to report vulnerabilities.
Pass
Adoption & popularityestablished adoption
A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.
Not checked
Signed releasesnot evaluated
Signed releases let consumers verify artifacts weren't tampered with.
N/A
No install/post-install scriptsguardno published package
install hooks run arbitrary code on every consumer at install time.
N/A
Package name not typosquattingguardno published package
Names mimicking popular packages are a common malware delivery vector.
N/A
Published with provenanceno published package
Build provenance attests the artifact was built from the claimed source by CI.
N/A
Established maintainerno published package
Brand-new / single anonymous maintainers raise takeover and malware risk.

Transport & Trust Model

Warn
Network Exposurebinds 0.0.0.0
Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.
Fix: Bind to 127.0.0.1 by default; never ship open debug endpoints.
Pass
Execution Sandboxingcontainerized
A container/sandbox image limits blast radius; a server that runs natively has full host access.
N/A
Transport Encryption (TLS)guardno remote endpoints
Plaintext HTTP exposes traffic and bearer tokens to interception.
N/A
IAM / Authentication Scopingno remote endpoints
OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.
N/A
Live Endpoint Reachablenot dynamically scanned
A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.
N/A
Authentication Enforced (live)not dynamically scanned
If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Embed this score

Add the live badge to your README — it updates automatically on every rescan.

markdown

[![Canopii Trust Score](https://index.canopii.dev/api/badge/Blazemeter/bzm-mcp)](https://index.canopii.dev/server/Blazemeter/bzm-mcp)

html

<a href="https://index.canopii.dev/server/Blazemeter/bzm-mcp"><img src="https://index.canopii.dev/api/badge/Blazemeter/bzm-mcp" alt="Canopii Trust Score" /></a>

Versions

Version	Score	Status	Published
vmain@6a43033latest	92A	scored	8/5/2026

Wondering how this compares? The MCP Security Index tracks grade distribution, committed secrets, and missing authentication across the whole ecosystem, refreshed monthly.