The BlazeMeter MCP Plugin for JMeter v1.0 enables performance teams to check, automate, and load test MCP servers over STDIO, SSE, and Streamable HTTP. Released on October 11, 2026, BlazeMeter 4.1 also introduces reduced Taurus Cloud image choices and addresses identified security vulnerabilities.
MCP server testing in JMeter
The BlazeMeter MCP Plugin for JMeter v1.0 brings MCP server testing into JMeter. Teams can use existing JMeter test plans, assertions, listeners, and thread groups when testing MCP servers through STDIO, SSE, or Streamable HTTP.
This change applies to teams using JMeter for performance testing that need to exercise MCP server interactions within familiar test-plan structures.
JMeter-only and empty Taurus Cloud images
Taurus Cloud now offers two image options intended to reduce bundled third-party executors:
- A JMeter-only Taurus Cloud image.
- An empty image that loads supported executors when a test starts.
The empty image supports only selected executors. It may need internet access or a custom executor download URL. Reducing unused executors can reduce CVE findings for components an organization does not use.
Taurus Cloud vulnerability fixes
Taurus Cloud version 2.4.538-reduced applies required fixes and removes affected components for three identified high-severity vulnerability entries:
CVE-2026-80212inresolvfor Ruby.CVE-2026-84304ingoogle.golang.org/grpc/internal/transportfor k6.CVE-2026-84304ingoogle.golang.org/grpc/memfor k6.
Based on the official Perforce release notes.
How Merito helps
Merito can help teams adopt and govern these BlazeMeter capabilities, including Taurus Cloud image selection, MCP test design, and test evidence expectations. See Managed Services.
Merito is an authorized Perforce reseller and services partner. Our Perforce BlazeMeter team helps you adopt the 4.1 changes, with implementation services to configure them for your environment and training and enablement to bring your teams up to speed.