Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/vjgit-369/jmeter-mcp-server-tsInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/vjgit-369/jmeter-mcp-server-ts/jmeter)<a href="https://agentmods.dev/mcp/vjgit-369/jmeter-mcp-server-ts/jmeter"><img src="https://agentmods.dev/badge/mcp/vjgit-369/jmeter-mcp-server-ts/jmeter/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/vjgit-369/jmeter-mcp-server-ts/jmeter"><img src="https://agentmods.dev/badge/mcp/vjgit-369/jmeter-mcp-server-ts/jmeter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
jmeter scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"jmeter": {
"command": "node",
"args": [
"C:/Users/Vijay/Documents/jmeter-mcp-server-ts/dist/index.js"
],
"env": {
"JMETER_HOME": "C:/apache-jmeter-5.6.3"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 11 lines scan A 20708979f347
jmeter is an MCP server published in the GitHub repository vjgit-369/jmeter-mcp-server-ts (0 stars, last pushed 11mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
jmeter compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| jmetervjgit-369/jmeter-mcp-server-ts | MCP server | 0 | 11mo ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| docs-langchainlangchain-ai/langchain | MCP server | 149k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| component-explorermicrosoft/vscode | MCP server | 195k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| codex_message_boardopenai/codex | MCP server | 134k | today | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| reamorluto/rea | MCP server | 443k | yesterday | MIT | A | — | Claude Code |
| reference-langchainlangchain-ai/langchain | MCP server | 149k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| playwright-testmicrosoft/playwright | MCP server | 100k | today | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |