API Auto Test FrameworkBLOCK
A YAML-first API testing framework built for AI-assisted API workflows.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
YAML Declarative API Testing Framework, Optimized for AI Coding Assistants
Case study | AgentsGalaxy | GitHub
Quick Start | MCP Integration | YAML Spec | Unit Testing
Why This Framework?
When asking AI to write API tests, you might encounter these issues:
Scenario 1: Repetitive Work
Every time you ask AI to generate tests, you need to re-describe the project structure, authentication method, and assertion style. For 10 API tests, the same fixture and setup code gets generated 10 times.
Scenario 2: Token Black Hole
A simple login API test generates 200 lines of code. You find an assertion is wrong, ask AI to fix it, and it generates another 200 lines. After 3 revisions, you've consumed 2000+ Tokens, and you still end up fixing it manually.
Scenario 3: Debugging Dead Loop
AI-generated tests fail to run. You paste the error message, AI fixes it but still wrong. After 5 rounds of conversation, the problem persists, and you've burned 5000+ Tokens.
This Framework's Solution:
Traditional: Natural Language -> AI Generates Full Code -> Run Error -> Paste Error -> AI Regenerates -> Loop... This Framework: Natural Language -> AI Generates YAML -> Framework Executes -> Locate Issue -> Fix 1 Line YAML
c8edc38c8727OBSERVED · 2026-10-09Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add api-auto-test --env MCP_AUTH_TOKEN=${MCP_AUTH_TOKEN} -- uvx api-auto-test{
"mcpServers": {
"api-auto-test": {
"command": "uvx",
"args": [
"api-auto-test"
],
"env": {
"MCP_AUTH_TOKEN": "${MCP_AUTH_TOKEN}"
}
}
}
}Exposed tools (6)
3 read · 2 write · 1 destructive. Blast radius: 1 tool can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
delete_testcase | destructive | deleted_files: list[str] = [] |
get_mcp_metrics | read | request_id = new_request_id() |
get_test_results | read | 获取测试执行历史 |
health_check | read | request_id = new_request_id() |
write_testcase | write | request_id = new_request_id() |
write_unittest | write | request_id = new_request_id() |
Trust audit
BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (4 observation(s))
- Network
- declared (5 observation(s))
- Shell
- declared (2 observation(s))
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (12)
return eval(f"dict({args_str})")return importlib.import_module(f'atf.utils.{module_name}')delete_testcase
config_path = os.path.join(os.path.dirname(os.path.abspath(__file__)), "../../config.yaml")
host: http://192.168.1.100:8080
url: http://192.168.1.100:8080/login
host: http://192.168.1.100:8080
url: http://192.168.1.100:8080/login
proxy_pass http://127.0.0.1:8000;
docs/images/mcp-architecture.png
curl -LsSf https://astral.sh/uv/install.sh | sh
curl -LsSf https://astral.sh/uv/install.sh | sh
Gates applied: no_behavioural_pass.
c8edc38c8727full audit observations/trust-audit/mcp-server/galaxyxieyu__api-auto-test-framework.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | c8edc38c8727 | BLOCK | D | 69 | first audit |
Questions
What is the API Auto Test Framework MCP server?
A YAML-first API testing framework built for AI-assisted API workflows.
What tools does API Auto Test Framework expose?
6 in total: 3 read-only, 2 that write, and 1 that can delete or overwrite (delete_testcase). Every one is listed on this page with its risk.
Is API Auto Test Framework safe to connect to an agent?
No — not without reading the findings first. The audit graded it D (69/100) and found 1 critical or high issue in the source. Each one is listed on this page with the file and line it is on. Separately from the audit: 1 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does API Auto Test Framework need?
It reads MCP_AUTH_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How current is this page?
The grade is for one exact copy of the source (c8edc38c8727), read on 2026-10-09. The repository is watched and re-audited when it changes.