Qa Probe vs Yandex Lavka MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Qa Probe vs Yandex Lavka MCP
In-depth architectural comparison of the Qa Probe and Yandex Lavka 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
Yandex Lavka MCP
Delivery · Local stdio
Quality: 53/100 (Good) | Auth: other
Verdict Summary: Choose Qa Probe if you need specialized Delivery tools running via a local process. Choose Yandex Lavka 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.
You need dedicated capabilities in the Delivery domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: YANDEX_LAVKA_MCP_TRANSPORT, YANDEX_LAVKA_MCP_CONFIG_JSON.
Primary tools included: Session and location management with saved addresses, Product search and detailed product info retrieval, Cart viewing, adding, updating, and clearing.
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
Order groceries from Yandex Lavka (Russia): search the catalog, build a cart, and place an order with a two-step confirmation before any charge. Unofficial (reverse-engineered private web API); local stdio or remote HTTP with OAuth. uvx yandex-lavka-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, Yandex Lavka MCP belongs to Delivery using local stdio subprocess. Select Qa Probe when you need capabilities focused on delivery and Yandex Lavka MCP when you require tools for delivery.