Qa Probe vs Amendor MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Qa Probe vs Amendor MCP
In-depth architectural comparison of the Qa Probe and Amendor MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Qa Probe
Delivery · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Amendor MCP
Delivery · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Qa Probe if you need specialized Delivery tools running via a local process. Choose Amendor MCP if your workspace requires Delivery integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Qa Probe when:
You need dedicated capabilities in the Delivery domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: QA_USER, QA_PASS.
Probes your live API and classifies why each endpoint failed (root cause + evidence + calibrated confidence) over MCP, so your AI assistant debugs from evidence instead of guessing. Deterministic rules, no black box. Works with FastAPI, Express, Next.js, tRPC, and GraphQL. npm i -g qa-probe
Lets the non-technical people you build for request UI changes directly on your live site, then pulls each request (with the exact element and page) into your coding agent so it builds it on a branch and opens a pull request. Works with Claude Code, Cursor, Cline, Codex, and remote agents over HTTP. npx -y amendor-mcp
Category & Scope
Tools & Capabilities Breakdown
Qa Probe Tools (8)
qa_probe_get_report
"Show me all broken routes and their scores"
qa_probe_explain_failure
"Why is /reports showing no data?"
qa_probe_probe_endpoint
"Is GET /users returning data right now?"
qa_probe_get_graph
"Which backend routes does /dashboard call?"
qa_probe_get_blast_radius
"What pages break if the users endpoint goes down?"
qa_probe_suggest_fix
"What should I do about feature_flag_disabled?"
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Qa Probe is categorized under Delivery and uses a local stdio subprocess. In contrast, Amendor MCP belongs to Delivery using local stdio subprocess. Select Qa Probe when you need capabilities focused on delivery and Amendor MCP when you require tools for delivery.
List change requests submitted by end users on sites you ship. Optionally filter by status. Start here to see what people are asking for.
get_change_request
Get full detail for one change request so you can implement it: the user request, the exact element they pointed at (CSS selector + outerHTML), the page URL, and a screenshot URL. Call this before making the change.
set_preview_url
Attach a deploy-preview URL to a change request and mark it ready for the requester to review.
update_status
Update a change request status as it moves through the build and review flow.
start_build
LOCAL MODE ONLY (repo on this machine, no host). Cuts a branch + git worktree the local Amendor serves at /preview/<id>/. For the normal GitHub flow, do NOT call this: instead branch "relay/task-<id>" in your own repo clone, edit, commit, push, and open a PR tagged "relay-task:<id>" — the host builds the preview and the webhook captures it automatically.
publish_preview
Mark a change request ready for the requester to review. The preview is already live from the worktree; this flips status to "in preview" and surfaces the link.
ship_change
Ship an approved change: merge the task branch into the project base, remove the worktree, and mark it shipped. Production (the live site) now reflects the change.