stresix
Registry code: 4ded3599d2509821
Stresix load tests a web app on a real server: it builds the user's GitHub repository or Docker image on a fresh cloud server, sends up to 10,000 simulated users at it, and reports what ran out first, p95 latency, error rate and what server size to run it on. No test script is needed.
Use start_load_test with the repository URL or image, the port the app listens on and a few paths worth testing (read the code to find them). Paid runs cost credits: when the tool answers with a price, ask the user before calling it again with confirm_spend set to true. Then poll get_test_status about once a…
- endpoint
- https://stresix.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is stresix live?
- Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
- Is stresix free to use?
- No — it asks for a key or a login before it will serve.
- What tools does stresix have?
- 3 tools: get_test_report, get_test_status, start_load_test.
- Is stresix safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_test_report auth-required 58m ago
The report of a finished run: the verdict, how many users it held, p95 latency, error rate, what ran out first and what to change or which server size to pick. Without a test_id it reports the latest run.
{ "type": "object", "properties": { "test_id": { "type": "string", "description": "The run id start_load_test returned." } }, "additionalProperties": false }arguments 10 linesget_test_status auth-required 58m ago
Where a run stands: building, starting servers, running (with live users, requests per second, p95 latency and error rate) or finished. Without a test_id it reports the latest run.
{ "type": "object", "properties": { "test_id": { "type": "string", "description": "The run id start_load_test returned." } }, "additionalProperties": false }arguments 10 linesstart_load_test auth-required never probed
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 GitHub account (500 users, 4 minutes). Standard (2,500 users, 10 minutes) costs 1 credit and Massive (10,000 users, 15 minutes) costs 3. A paid run is only started with confirm_spend set to true, and only after the user has agreed to the price. Without a tier it uses the free Lite run when the account still has it.
{ "type": "object", "required": [ "target" ], "properties": { "env": { "type": "object", "description": "Environment variables the app needs to boot, such as NODE_ENV or a test database URL. Stored encrypted and wiped after the run. Never send production secrets.", "additionalProperties": { "type": "string" } }, "port": { "type": "integer", "maximum": 65535, "minimum": 1, "description": "The port the app listens on inside its container. Read it from the code. Stresix tries 80, 3000, 5000, 8000 and 8080 when it is left out." }, "tier": { "enum": [ "lite", "standard", "massive" ], "type": "string", "description": "Run size. Leave it out to use the free Lite run when available." }, "paths": { "type": "array", "items": { "type": "string" }, "maxItems": 10, "description": "GET paths the simulated users rotate through, for example [\"/\", \"/api/products\", \"/search?q=shoes\"]. Pick pages that hit the database. Defaults to [\"/\"]." }, "branch": { "type": "string", "description": "Repository branch to build. The default branch when left out." }, "target": { "type": "string", "description": "GitHub repository URL (https://github.com/owner/repo) or a Docker image (nginx:1.27, ghcr.io/owner/app:tag)." }, "confirm_spend": { "type": "boolean", "description": "Set to true only after the user agreed to spend credits on this run." } }, "additionalProperties": false }arguments 51 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id4ded3599d2509821.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4ded3599d2509821/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4ded3599d2509821?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.