Remote MCP · Endpoint
JMeter Docs MCP server
No. JMeter Docs answered an MCP handshake 5 hours ago.
UpLast checked 5 hours ago
Server URL
https://docs.jmeter.ai/api/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.QAInsights/jmeter-docs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 581 ms
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 94.1% from 17 checks
- Described by its publisher as
- Apache JMeter community documentation, conversion tools, linters, and calculators for AI agents.
- Website
- https://docs.jmeter.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Handshake completed | 581 ms |
| 2 days ago | Handshake completed | 1.01 s |
| 4 days ago | Handshake completed | 464 ms |
| 5 days ago | Handshake completed | 450 ms |
| 7 days ago | Handshake completed | 565 ms |
| 8 days ago | Handshake completed | 470 ms |
| 9 days ago | Handshake completed | 631 ms |
| 12 days ago | Handshake completed | 551 ms |
| 13 days ago | Handshake completed | 816 ms |
| 15 days ago | Handshake completed | 1.01 s |
| 16 days ago | Handshake completed | 375 ms |
| 17 days ago | Handshake completed | 407 ms |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Handshake completed | 315 ms |
| 20 days ago | Handshake completed | 417 ms |
| 21 days ago | Handshake completed | 707 ms |
| 22 days ago | Handshake completed | 340 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 17.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with JMeter Docs and makes no claim about it beyond what these checks measured.