ReqStorm is an Model Context Protocol (MCP) server for API testing, performance analysis, contract validation, fuzzing, and lightweight security checks. It runs over stdio, so it works with MCP…
reqstorm is an MCP project maintained in the looph0le/reqstorm repository. The maintainer describes its purpose as “ReqStorm is an Model Context Protocol (MCP) server for API testing, performance analysis, contract validation, fuzzing, and lightweight security checks. It runs over stdio, so…”. Read the project documentation for the complete scope.
The documented npm package is reqstorm. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| benchmark | Measure throughput and p50/p95/p99/p999 latency. Results include overall, warm-up, and steady-state data. |
| smoke | Quickly check that an endpoint responds with the expected status and body. |
| load-test | Run sustained traffic and evaluate steady-state maxP95, maxP99, and maxErrorRate thresholds. |
| spike | Run baseline, sudden surge, and recovery phases; measure recovery against baseline latency. |
| soak | Run long-lived traffic in periodic chunks to find memory leaks, exhaustion, and performance drift. Default duration is 30 minutes. |
| stress-test | Ramp concurrency step by step until latency or error-rate thresholds identify a breaking point. |
| compare | Compare two endpoints or configurations side by side, optionally repeating each target up to five times. |
| validate | Send one request and assert on JSONPath values, types, comparisons, regexes, array properties, and response-time thresholds. |
| chain | Execute up to 20 ordered requests, extract values from responses, interpolate them into later requests, and assert each step. |
| contract-check | Check a running API against an OpenAPI 3.x JSON/YAML document, including status codes, schemas, content types, and required fields. |
| fuzz | Mutate request bodies with boundary, type-swap, injection, overflow, missing-field, Unicode, format, and null-field strategies. |
| regression | Compare steady-state performance with a saved .reqstorm/ baseline and optionally save the current run as the new baseline. |
| security-scan | Run selected checks for authentication bypass, IDOR, security headers, data exposure, rate limiting, method override, content-type mismatch, and path… |
| profile | Inspect latency distribution, status-code counts, throughput stability, and error/timeout breakdowns. |
{
"mcpServers": {
"reqstorm": {
"command": "npx",
"args": [
"-y",
"reqstorm"
]
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.