Qarunbook is answering right now. Last checked 1 min ago. It exposes 14 tools.
Shared app-testing runbook: read the plan, record results per platform, raise and fix issues.
Uptime history
2 hours of history
2 hours agonow
100.0%
Uptime 24h
4 of 4 checks
14
Tools
read from the server
510 ms
Response time
average over 24h
open, no key
Access
streamable-http
Nothing serious here today
Today is the operative word: we check Qarunbook every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
run in your terminal
claude mcp add qarunbook --transport http https://qarunbook.com/api/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"qarunbook": {
"url": "https://qarunbook.com/api/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.qarunbook]
url = "https://qarunbook.com/api/mcp".cursor/mcp.json
{
"mcpServers": {
"qarunbook": {
"url": "https://qarunbook.com/api/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"qarunbook": {
"url": "https://qarunbook.com/api/mcp"
}
}
}Available tools 14
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
add
add_check
Add a check to a section. Its reference is generated as the next number in that section's series. Steps should be followable by someone who has never seen the code.
app
create_app
Add an app to the runbook. Give it a name and the platforms it is tested on. Then use add_section and add_check to fill it in — or upload a markdown test plan through the web app, which is faster for a whole plan.
apps
list_apps
List the apps in the runbook, with their platform codes and how many checks each has. Call this first to get an app name to pass to the other tools.
checks
list_checks
Checks in an app, with their derived status per platform. Filter to 'failing' to see what is broken, 'retest' for fixes nobody has verified yet, 'untested' for what nobody has looked at.
edit
edit_issue
Reword an issue, or change which platforms it affects — when a report is vague, wrong, or missing the exact error. The original reporter stays on it, you are recorded as the editor, and the previous wording is kept in its history.
get
get_check
One check in full by its reference, e.g. 'AUTH-01': preconditions, steps, expected result, status on each platform, and every issue against it.
import
import_plan
Create a whole app from a markdown test plan, in one call. This is how to add a real runbook — a plan runs to hundreds of checks and add_check one at a time is not the way. Sections come from the '##' headings, checks from the table rows beneath them, and the platform columns from the check table's header. Pass the file's contents as text.
issue
add_issue
Raise an issue against a check. This takes the pass away on the platforms it affects, until it is marked fixed. Leave platforms empty to mean every platform.
issues
list_issues
Issues testers raised, newest first — the text they wrote, who raised it, which platforms it affects, and which check it is against. Defaults to open issues only. This is the main thing to read before fixing anything.
progress
progress
Coverage summary for an app: how many platform-checks are passing, failing, untested or not applicable, and how many issues are open. Use it to answer 'where is testing up to'.
resolve
resolve_issue
Mark an issue fixed, or reopen it. Fixing restores whatever mark was underneath — a check that was passing before the issue goes back to passing, and one that was never tested goes back to untested.
result
set_result
Record a tester's result for one check on one platform: 'P' passed, 'F' failed, '' clears it back to untested. An open issue still overrides this while it is open, and recording a result is what clears an 'R' (retest) after a fix.
section
add_section
Add a section to an app — a module or feature area. Its reference is the prefix its checks are numbered against, so 'SUP' gives SUP-01, SUP-02. No two sections in an app may share one.
update
update_check
Correct a check — its wording, or which platforms it applies to. Use when a step is wrong or misleading, or when a check does not belong on a platform at all. Pass not_applicable_on to mark it N/A there; it then stops counting towards coverage on those platforms. The reference is not editable; it is a position in the section's series.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://qarunbook.com/api/mcp | streamable-http | answering | 1212 ms | 1 min ago |
Alternatives to Qarunbook
same job, measured the same wayPlaywright Report MCP
by hubertgajewski
Run Playwright tests and surface structured results for AI agents doing test failure analysis.
Flutter Skill
by telsav
AI E2E testing bridge — give AI eyes and hands inside any app. 8 platforms, 40+ tools.
Loadster
by loadster
Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots.
agentgate
by ciceroyang
Read-only evidence for the tools agents run: MCP server records, coverage and policy.
Decisionrules
by decisionrules
Create, manage, and test business rules directly from your AI agent via the DecisionRules platform.
Word Is Bond
by latimer-woods-tech
Test the voice agents you run: scored transcripts, pass/fail verdicts, latency and WER metrics.
ProdPoke
by prodpoke
AI QA tester — real browsers scan sites for bugs, SEO, perf, and accessibility issues via chat.
AudioEye Accessibility Testing
by audioeye
Scans live pages with the AudioEye rules engine and maps accessibility issues to JSX source.
Qarunbook — questions
Answers built from our own checks of this server.
What can Qarunbook do?
It exposes 14 tools, read directly from the server on our last check. Among them: add_check, add_issue, add_section, create_app, edit_issue, get_check and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Qarunbook working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 4 of 4 checks got a reply (100.0%), average response time 510 ms. The bar chart above shows every period we have measured.
How do I connect Qarunbook?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Qarunbook need an API key?
No. Qarunbook completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Qarunbook?
It answers our handshake in 510 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.