Skip to content
Stresix logo

Stresix MCP server

Which MCP servers are Stresix's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to Stresix

Whose server it is
  • Registry namecom.stresix/stresixverified in the MCP registry

The registry name sits under stresix.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools14
  • Server calls itselfstresix
  • Server version1.1.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 183 ms.

Should an agent connect itSkip it
  • Answered on only 2 of 7 daily checks.
  • Its tools do every use case we checked: Load test a web app without writing scripts; Find whether CPU, memory or the database runs out first; Check whether a bigger server would actually help.

Once connected

  • For "Load test a web app without writing scripts", the likely first call is start_load_test.
  • Keep approval on for send_feedback: they delete, send or pay without saying so.
  • delete_load_test, set_current_server, send_feedback change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-27
  • INITE MCP score49 of 100answers 29 · does the job 100 · definitions 100 · context 100 · use 0 · connects 100 · lowered by the warning signs below
  • What an agent can do with it3 of 3 use cases
  • Answered29% of days2 of 7 daily checks
  • Median first answer604 ms
  • Space in an agent's context≈ 2,452 tokensthe definitions of all its tools (14), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 14 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Load test a web app without writing scripts
  • can do · Find whether CPU, memory or the database runs out first
  • can do · Check whether a bigger server would actually help

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that delete, send or pay, marked as not destructive: send_feedback
  • Tools that change data, on a server that answers without a sign-in: delete_load_test, set_current_server, send_feedback

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers14 tools · read 2026-10-27
  • start_load_test

    Load tests the user's app on a real cloud server and returns a run id. The target is a public or connected GitHub repository URL, or a Docker image. Lite is free once per person (500 users, 4 minutes). Standard (2,500 users, 10 minutes)…

  • get_test_status

    Where a run stands: building, starting servers, running (with live users, requests per second, p95 latency and error rate) or finished.

  • get_test_report

    The full report of a finished run: the verdict, users held, requests per second, p95 latency and errors at each load level, what ran out first, CPU, busiest thread and memory on the server and per service, connections to the database and…

  • get_test_timeline

    How a run moved over time: users, requests per second, p95 latency and error rate, averaged into a fixed number of points. Works while a run is going and after it ends.

  • list_load_tests

    The account's runs, newest first: id, status, size, target, requests, when it ran and why it failed if it did.

  • stop_load_test

    Stops a run that is waiting or running and deletes its servers. A run stopped before its servers were up uses no credit. A run stopped while the load is going is not refunded, and its report covers what was measured until then. Ask the…

  • delete_load_test

    Deletes a run and its report and measurements for good. A running run has to be stopped first. Ask the user first.

  • set_current_server

    Tells a run which server the user already hosts the app on, so the report says whether that server is enough, how close to the limit it would be and what to change. Or set recommend to true to go back to a recommended size. The report is…

  • send_feedback

    Tells Stresix whether a finished run's report was useful, with an optional note. Only send what the user actually said. Sending again replaces the earlier answer.

  • inspect_target

    Reads a repository before testing it: the port it listens on, the environment variables the code reads, the framework, whether it needs a database, and its branches. For a Docker image it only checks the reference. Use it before…

  • list_github_repos

    The GitHub repositories the user gave Stresix access to, including private ones. Public repositories work without connecting GitHub.

  • get_account

    The account's credits, whether the free Lite run is still available, whether GitHub is connected, what each run size costs and the credit packs on sale.

  • buy_credits

    Makes a checkout link for a credit pack: Starter is 5 credits for $10, Pro is 25 credits for $40. Nothing is charged by this tool. The user opens the link and pays in their browser, and the credits arrive a minute later. Only call it when…

  • redeem_code

    Adds the credits of a promo code to the account. Only use a code the user gave you.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "stresix": {
      "type": "http",
      "url": "https://stresix.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http stresix https://stresix.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://stresix.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.