JMeter Docs
REMOTE · DOCS.JMETER.AI
Apache JMeter community documentation, conversion tools, linters, and calculators for AI agents.
Available components
Last scanned (20 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3052 tokens (~190/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 18 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “get_correlation_sandbox” functional
- 9 Oct 26 +1
- Stability: 0.93 → pass security
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 93. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1653 → 1846 ▼ functional
- New tool “lookup_component” functional
- New tool “lookup_function” functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 4 Nov 2026 · Probed https://docs.jmeter.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jmeter.ai | CN=WE1,O=Google Trust Services,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3ae4a6c171f5465e1349a9be2e37e53b |
| SANs: jmeter.ai, docs.jmeter.ai, *.docs.jmeter.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of docs.jmeter.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| jmeter.ai. | present | 2371 | 13 | Verified |
| docs.jmeter.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docs.jmeter.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://docs.jmeter.ai/api/mcp | Served over HTTP | 200 |
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 →
calculate_workload_model Calculate Workload Model & Little's Law Sizing ~149
Compute required thread concurrency, pacing delays, ramp-up schedules, and JVM heap recommendations based on target RPS/TPS and SLA response times using Little's Law.
| Name | Type | Req | Description |
|---|---|---|---|
| avgResponseTimeMs | number | yes | Expected average response time in milliseconds. |
| safetyFactor | number | – | Headroom safety buffer multiplier (default: 1.25 = 25% buffer). |
| targetRps | number | yes | Target throughput in requests / transactions per second (RPS/TPS). |
| testDurationMinutes | number | – | Steady-state test duration in minutes (default: 10). |
| thinkTimeMs | number | – | Think time / user pause between requests in milliseconds (default: 0). |
No output schema declared.
No examples provided.
convert_curl_or_har_to_jmx Convert cURL or HAR to JMeter JMX Test Plan ~326
Convert one or more cURL commands or HAR (HTTP Archive 1.2) JSON traces into a valid, production-ready Apache JMeter .jmx test plan XML with HTTP Request Defaults, Header Managers, Cookie Managers, timeouts, and assertions. Supports GET, POST, PUT, DELETE, PATCH, and RFC 9838 QUERY methods.
| Name | Type | Req | Description |
|---|---|---|---|
| durationSeconds | integer | – | Test duration in seconds (0 = disabled, default: 0). |
| filterStaticAssets | boolean | – | Filter out images/css/fonts when parsing HAR (default: true). |
| includeAssertions | boolean | – | Add HTTP 200/201/204 Response Code assertions (default: true). |
| includeCookieManager | boolean | – | Include HTTP Cookie Manager (default: true). |
| input | string | yes | cURL command string (single, multiline, or batch) or HAR 1.2 JSON text (max 1MB). |
| loopCount | integer | – | Loop count (-1 for infinite, default: 1). |
| parameterizeAuth | boolean | – | Extract Bearer token into ${AUTH_TOKEN} variable (default: true). |
| parameterizeHost | boolean | – | Extract common host into HTTP Request Defaults and ${BASE_URL} (default: true). |
| rampUpSeconds | integer | – | Ramp-up time in seconds (default: 1). |
| testPlanName | string | – | Name of the JMeter Test Plan (default: "cURL Converted Plan"). |
| threads | integer | – | Thread concurrency / virtual users (default: 1). |
No output schema declared.
No examples provided.
convert_openapi_to_jmx Convert OpenAPI / Swagger to JMeter JMX Test Plan ~440
Convert an OpenAPI 3.0/3.1 or Swagger 2.0 document (JSON or YAML) into a JMeter 5.6.3 .jmx test plan: servers become HTTP Request Defaults/${BASE_URL}, path parameters become User Defined Variables, request bodies are sampled from schemas, bearer/basic/apiKey security becomes ${AUTH_TOKEN}/${BASIC_AUTH}/${API_KEY}, with optional method, tag, and deprecated-operation filters.
| Name | Type | Req | Description |
|---|---|---|---|
| durationSeconds | integer | – | Test duration in seconds (0 = disabled, default: 0). |
| includeAssertions | boolean | – | Add HTTP 200/201/204 Response Code assertions (default: true). |
| includeCookieManager | boolean | – | Include HTTP Cookie Manager (default: true). |
| includeDeprecated | boolean | – | Include deprecated operations (default: false). |
| includeOptionalQueryParams | boolean | – | Include optional query parameters (default: false). |
| input | string | yes | OpenAPI 3.x or Swagger 2.0 document as JSON or YAML text (max 1MB). |
| loopCount | integer | – | Loop count (-1 for infinite, default: 1). |
| maxOperations | integer | – | Maximum number of operations to convert (default: 500). |
| methods | array | – | HTTP methods to include (default: GET, POST, PUT, PATCH, DELETE). |
| parameterizeHost | boolean | – | Extract the common host into HTTP Request Defaults and ${BASE_URL} (default: true). |
| rampUpSeconds | integer | – | Ramp-up time in seconds (default: 5). |
| serverIndex | integer | – | Zero-based index of the OpenAPI server to use (default: 0). |
| tags | array | – | Only include operations with one of these tags ("default" = untagged). Empty = all. |
| testPlanName | string | – | Name of the JMeter Test Plan. |
| threads | integer | – | Thread concurrency / virtual users (default: 10). |
| useExampleValues | boolean | – | Substitute example/sample values into path params instead of ${var} variables (default: false). |
No output schema declared.
No examples provided.
get_correlation_sandbox Get Correlation & Practice Sandbox Test Plan ~227
Generate a ready-to-run Apache JMeter 5.6.3 .jmx practice test plan (either "solved" with Boundary/JSON/Header extractors or "challenge" with broken hardcoded tokens) targeting the live docs.jmeter.ai/api/sandbox endpoints or local localhost:8787 server.
| Name | Type | Req | Description |
|---|---|---|---|
| flowId | string | – | Practice flow: "flow1" (CSRF + Cookie), "flow2" (JWT Bearer + Order chain), "flow3" (ASP.NET __VIEWSTATE + Header ticket), or "flow4" (HTTP 429 & JSON Assertion chaos). Default: "flow1". |
| mode | string | – | "solved" returns a working correlated .jmx plan; "challenge" returns a broken plan with hardcoded recorded tokens for debugging practice. Default: "solved". |
| target | string | – | "edge" targets https://docs.jmeter.ai/api/sandbox (1-thread debug); "local" targets http://localhost:8787/api/sandbox (high-RPS). Default: "edge". |
No output schema declared.
No examples provided.
get_jmeter_page Read a JMeter documentation page ~87
Fetch the full markdown text of one docs.jmeter.ai page. Accepts the page URL (e.g. https://docs.jmeter.ai/topics/api-load-testing/) or a bare path (e.g. topics/api-load-testing).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Page URL or path, e.g. https://docs.jmeter.ai/user-manual/functions/ or user-manual/functions |
No output schema declared.
No examples provided.
get_jsr223_recipe Get Verified JSR223 Groovy Recipe ~105
Fetch production-ready, performant Groovy scripts for JMeter JSR223 samplers, preprocessors, and postprocessors (e.g., JWT parsing & expiration, HMAC-SHA256 signing, dynamic header injection, nested JSON array extraction, custom CSV failure logging).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Filter by keyword or topic (e.g. "jwt", "hmac", "header", "json", "csv", "logging"). If omitted, returns all recipes. |
No output schema declared.
No examples provided.
lint_groovy_script Lint JMeter Groovy (JSR223) Script ~169
Statically analyze a Groovy script for a JMeter JSR223 element. Flags Thread.sleep, ${var} interpolation, System.out, BeanShell APIs, per-call Random or Pattern.compile, and bindings such as prev, SampleResult, or sampler that the selected element type does not expose; optionally returns ready-to-paste JMX element XML.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Groovy script source. |
| elementType | string | – | (default: JSR223PostProcessor) |
| includeJmxElement | boolean | – | Also return the JSR223 element XML with compilation caching enabled (default: true). |
| name | string | – | testname for the generated JMX element (default: element label). |
| parameters | string | – | Space-separated parameters available through Parameters and args. |
No output schema declared.
No examples provided.
lint_jmx_snippet Lint JMX Test Plan Snippet ~87
Validate a JMeter test plan XML string or snippet against best practices and performance anti-patterns, and return a structural inventory with thread groups, sampler/listener/assertion counts, HTTP Defaults/Header/Cookie/CSV presence, plugin classes, and JMeter version.
| Name | Type | Req | Description |
|---|---|---|---|
| jmxContent | string | yes | JMX XML string or test plan snippet to analyze (max 1MB). |
No output schema declared.
No examples provided.
lookup_component Lookup JMeter Component Reference Page ~82
Find the dedicated reference page for a JMeter test plan component (e.g. "HTTP Request", "JSON Extractor", "Thread Group") and return its full markdown content with properties, defaults, and related guides.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Component name, exact or partial (e.g. "HTTP Request", "JSON Extractor", "CSV Data Set"). |
No output schema declared.
No examples provided.
lookup_error_playbook Lookup Error & Exception Diagnostic Playbook ~150
Get immediate root causes, OS/JVM config fixes, and remediation steps for common JMeter exceptions (e.g. "BindException", "SocketTimeoutException", "OutOfMemoryError", "NoHttpResponseException", "SSLHandshakeException", "401/403 after recording"). When keywords miss, unmatched text is sent to classifier.dev for zero-shot semantic matching (public keyless calls are not stored).
| Name | Type | Req | Description |
|---|---|---|---|
| classifierApiKey | string | – | Your own classifier.dev API key for the semantic fallback (anonymous quota is shared); never logged. |
| query | string | yes | Error message, exception name, or status (e.g. "bindexception", "heap", "timeout", "401"). |
No output schema declared.
No examples provided.
lookup_function Lookup JMeter Function Reference Page ~75
Find the dedicated reference page for a built-in JMeter function (e.g. "__time", "__Random", "__P") and return its full markdown content with syntax, parameters, and examples.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Function name, with or without leading underscores (e.g. "__time", "time", "__RandomString"). |
No output schema declared.
No examples provided.
lookup_jmeter_property Lookup JMeter Tuning Property ~87
Search or lookup curated JMeter properties (e.g. "httpclient4.idletimeout", "jmeter.save.saveservice.*", "remote_hosts", "summariser"). Returns category, defaults, and recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Property name or keyword to search (e.g. "ssl", "timeout", "jtl", "influxdb"). |
No output schema declared.
No examples provided.
plan_distributed_testing Plan Distributed Testing Ports & Firewall Rules ~237
Generate Master-Worker RMI port assignments, user.properties, CLI commands, firewall/security group rules, and Docker Compose manifests for distributed load testing.
| Name | Type | Req | Description |
|---|---|---|---|
| clientRmiLocalPort | integer | – | Pinned controller callback port (default: 60000). |
| controllerIp | string | – | Controller / Master node IP or hostname (default: "10.0.0.5"). |
| disableSsl | boolean | – | Disable RMI SSL (default: false). Only for isolated labs. |
| environment | string | – | Target infrastructure environment for firewall/CLI rules (default: "aws"). |
| mode | string | – | Sample transmission mode (default: "StrippedBatch"). |
| serverPort | integer | – | RMI registry port on workers (default: 1099). |
| serverRmiLocalPort | integer | – | Pinned worker engine port (default: 50000). |
| workerIps | string | yes | Comma or space-separated list of worker / injector IP addresses (e.g. "10.0.1.10, 10.0.1.11, 10.0.1.12"). |
No output schema declared.
No examples provided.
search_jmeter_docs Search JMeter documentation ~85
Search the Apache JMeter documentation on docs.jmeter.ai. Returns the most relevant pages with titles, URLs, and snippets. Use for any question about JMeter test plans, components, functions, properties, distributed testing, reports, or troubleshooting.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query, e.g. "how to correlate dynamic values" or "thread group ramp up" |
No output schema declared.
No examples provided.
triage_errors Triage a Batch of JMeter Error Signatures ~161
Map a run's distinct failure signatures to docs.jmeter.ai error playbooks. Error text is sent to classifier.dev for zero-shot classification (public keyless calls are not stored; obvious secrets are redacted first). Prefer signatures shaped as "sampler | response code | response message".
| Name | Type | Req | Description |
|---|---|---|---|
| classifierApiKey | string | – | Your own classifier.dev API key (anonymous quota is shared); never logged. |
| errors | array | yes | Distinct error signatures to triage. |
| minConfidence | number | – | Confidence threshold for auto-bucketing a signature to a playbook (default: 0.7). |
| tier | string | – | Classifier tier (default: "fast"). "smart" re-asks only signatures below minConfidence (slower). |
No output schema declared.
No examples provided.
tune_linux_os Linux Kernel & OS Tuning for Load Injectors ~169
Generate production sysctl.conf, limits.conf, systemd overrides, and Docker/K8s configs tuned for high-concurrency JMeter load testing (fixing ulimit nofile, BindException port exhaustion, somaxconn backlog, and JVM swappiness).
| Name | Type | Req | Description |
|---|---|---|---|
| concurrency | integer | – | Target concurrent connections/threads (default: 10000). |
| ramGb | integer | – | Host machine RAM in GB for TCP buffer sizing (default: 16). |
| role | string | – | Machine role: "injector" (JMeter client) or "target_sut" (default: "injector"). |
| targetDistro | string | – | Linux distro or container target (default: "ubuntu_debian"). |
| trafficType | string | – | Traffic profile (default: "http_churn"). |
No output schema declared.
No examples provided.
How do I install the JMeter Docs MCP server?
JMeter Docs is a hosted endpoint at https://docs.jmeter.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · docs.jmeter.ai
claude mcp add --transport http qainsights-jmeter-docs 'https://docs.jmeter.ai/api/mcp'
What is the JMeter Docs MCP server?
JMeter Docs is an MCP server listed in the public MCP registry as io.github.QAInsights/jmeter-docs. Apache JMeter community documentation, conversion tools, linters, and calculators for AI agents. This page covers its hosted endpoint (https://docs.jmeter.ai/api/mcp).
Is the JMeter Docs MCP server safe to use?
JMeter Docs scores 74 out of 100 on VerifyMCP. 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.
What tools does the JMeter Docs MCP server expose?
JMeter Docs exposes 16 tools: search_jmeter_docs, get_jmeter_page, lint_jmx_snippet, calculate_workload_model, lookup_jmeter_property, and 11 more. Their descriptions and schemas cost roughly 2,636 tokens of context every time the server is loaded.
Does the JMeter Docs MCP server require authentication?
No. We connected to JMeter Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the JMeter Docs MCP server still maintained?
JMeter Docs is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.