Developer · Remote MCP server
TesterArmy
Agents that test your web and mobile app like real users, on every pull request.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.tester-army/testerarmy- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-21
- Updated
- 2026-09-21
- Publisher
- tester-army (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/tester-army) · how
- Website
- docs.tester.army/cli/mcp
- Repository
- github.com/tester-army/cli
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://tester.army/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect TesterArmy
TesterArmy is a remote MCP server: there is nothing to install. Its endpoint is https://tester.army/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| TerraVisionCloud architecture diagrams with official AWS, Azure and GCP icons, from Terraform or a JSON graph. | Local · stdio |
| Tessera MCP ServerMCP server for Tessera's LLM cost-optimization layer: anchored spend, drift, recommendations. | Local · stdio |
| tesseraiYour project's design system for coding agents: tokens, components, contrast checks, guidelines. | Local · stdio |
| TestAtlasSemantic map of a.NET test-automation solution for AI agents - search, impact, endpoints. | Local · stdio |
| Testkube MCPMCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants. | Remote & Local · HTTP, stdio |
| TestMu AI (formerly LambdaTest)Agentic testing: HyperExecute jobs, test failure triage, SmartUI visual diffs, a11y audits. | Remote · HTTPLive check: ✓ handshake |
| TestorimAI browser tests from your coding agent: a verdict, failing steps, report, video and trace. | Local · stdio |
| Testrail MCP ServerConnect AI assistants to TestRail: manage test cases, suites, runs, results, and attachments. | Local · stdio |