autotest-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRON_PAYOUT_ADDRESS | No | The TRON (TRC-20 USDT) payout address for the Web3 paywall. | |
| POLYGON_PAYOUT_ADDRESS | No | The Polygon (ERC-20 USDC) payout address for the Web3 paywall. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_edge_testsA | Synthesizes industrial-grade defensive unit tests with 96%+ branch coverage, boundary invariance, and exception handling for any source code. |
| audit_code_defensesA | Audits AST cyclomatic complexity, branch depth, and detects unhandled exception vectors in source code. |
| get_paywall_statusA | Retrieves official sponsorship wallet addresses, live Web3 paywall gateway, and pro tier pricing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a clearly distinct action and resource: generating tests, auditing code defenses, and fetching paywall status. Even though get_paywall_status is unrelated to the testing domain, there is no ambiguity between the tools.
All tool names follow a consistent snake_case verb_noun pattern: generate_edge_tests, audit_code_defenses, get_paywall_status. The naming convention is uniform and predictable.
Three tools is a reasonable count and not excessive, but the inclusion of get_paywall_status feels tangential to the autotest theme, and two core tools is a slightly small surface for a testing/auditing server.
The server can generate tests and audit code defenses, but there are no tools to run tests, retrieve generated test outputs, manage configurations, or handle results. The paywall status tool is unrelated and does not fill these workflow gaps, leaving the domain only partially covered.