MCP.Market

Qarunbook MCP server

online · 96% uptime
by Ifeanyiejindu·io.github.Ifeanyiejindu/qarunbook·v1.1.0
No reviews yet

Shared app-testing runbook: read the plan, record results per platform, raise and fix issues.

A97/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Qarunbook yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Qarunbook tools (14, 3 write)

write = sends, deletes, buys or posts
  • add_checkFree

    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.

  • add_issueFree

    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.

  • add_sectionFree

    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.

  • create_appwrite actionFree

    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.

  • edit_issueFree

    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_checkFree

    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_planwrite actionFree

    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.

  • list_appsFree

    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.

  • list_checksFree

    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.

  • list_issuesFree

    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.

  • progressFree

    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_issueFree

    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.

  • set_resultFree

    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.

  • update_checkwrite actionFree

    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.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 392ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 9 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Qarunbook compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,255 servers
Tools
14
the typical server has 7
Tools that change things
21%
typical: 0%. Fewer write tools means less an agent can break
Uptime
96%
of our recent checks; the typical remote server answers 100%
Response time
56 ms
faster than 91% of 30,031 servers

What its tools let an agent do: 6 read · 5 create · 3 change

Install Qarunbook in Claude Code, Cursor or VS Code

claude mcp add --transport http qarunbook https://qarunbook.com/api/mcp
Add to Cursor

What the publisher says

From the Qarunbook repository's README, as published. We do not edit it. Read it on GitHub

qarunbook

Work out what needs testing, then actually get it tested.

Most teams know they should test before a release. What stops them is not discipline — it is that nobody wants to sit down and write out three hundred things to check, and once somebody has, there is nowhere sensible to record what happened to each one.

qarunbook does both halves:

module, feature and user journey worth testing, across each platform you ship on, and writes them as checks a non-technical person can follow. Or write them yourself, or upload a plan you already have.

  1. Itemise. Point an AI assistant at your codebase and it works out every

failed and raising what breaks. You can see how far along the release is at any moment, and what is in the way.

  1. Test and track. Testers work top to bottom, marking each check passed or

It is built for user acceptance testing — the pass a human makes over a real build before it ships. Not unit tests, not CI. The kind of testing where somebody opens the app, signs up, and tries to actually use it.

https://qarunbook.com — free to use.

Why an MCP server

Because the loop usually breaks at the hand-off. A tester finds a bug, writes it in a spreadsheet or a WhatsApp message, and it is now somebody's job to read that, understand it, fix it, and remember to tell the tester it is done.

qarunbook exposes the runbook over MCP, so your coding assistant is on the other end of that loop directly:

list_issues            what did the testers actually find (and what they attached)
list_checks failing    what is broken right now
edit_issue             that report was vague — here is what actually happens
resolve_issue          I fixed it

Testers can attach screenshots, screen recordings and logs to an issue in the web app. Videos stream straight in the page, so a bug is something you watch rather than something you read about.

When an issue is marked fixed, the check does not silently go back to passing. It reads R — retest, because the person who last passed it was looking at a build without the fix in it. It clears when somebody actually looks again. Status is derived from marks and issues rather than stored, so the runbook can never quietly disagree with itself.

Install

Claude Code

One step, and the MCP connection and both skills come with it:

/plugin marketplace add Ifeanyiejindu/qarunbook
/plugin install qarunbook@qarunbook

(or from a terminal: claude plugin marketplace add Ifeanyiejindu/qarunbook then claude plugin install qarunbook@qarunbook)

Then set your token, from your qarunbook home page under Connect your AI:

export QARUNBOOK_TOKEN="qarb_…"

The token is yours, not the workspace's. It acts as you, with your role, and removing you revokes exactly it.

Updates

Open /plugin, choose Marketplaces, select qarunbook, and turn on auto-update — Claude Code checks when it starts. Or update by hand:

/plugin marketplace update qarunbook
/plugin update qarunbook@qarunbook
/reload-plugins

Codex, Cursor and other agents

Two parts: the MCP connection, and the skills.

1. The skills — works with Codex, Cursor, Gemini CLI, OpenCode, Cline and other agents that read SKILL.md files:

npx skills add Ifeanyiejindu/qarunbook --global

Update them later with npx skills update -g.

2. The MCP connection.

Codex — ~/.codex/config.toml

[mcp_servers.qa-runbook]
url = "https://qarunbook.com/api/mcp"
http_headers = { Authorization = "Bearer qarb_…" }

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "qa-runbook": {
      "url": "https://qarunbook.com/api/mcp",
      "headers": { "Authorization": "Bearer qarb_…" }
    }
  }
}

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Qarunbook: common questions

Is Qarunbook MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Qarunbook safety report
How do I install Qarunbook?
It runs remotely at qarunbook.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Qarunbook need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Qarunbook maintained?
The last commit was 10 days ago (2026-10-25). The latest release is v1.1.0.
Is Qarunbook up?
96% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Qarunbook compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,255 servers); tools 14 (the typical server has 7); tools that change things 21% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.