Skip to main content
Glama
Sign In

qarunbook

by io.github.Ifeanyiejindu
OverviewDiscussionsAdmin

Server Details

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

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
1.6% over 40 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
Repository
Ifeanyiejindu/qarunbook
GitHub Stars
0

TDQS

A4/5.0

Scored across 14 tools

Disambiguation5/5

Every tool targets a distinct action on a distinct resource: app creation, section/check management, result recording, issue lifecycle, and summary queries. There is no overlap between tools like add_issue and resolve_issue or set_result and list_checks; each has a clear and unique purpose.

Naming Consistency4/5

Most tools follow a verb_noun pattern in snake_case (add_section, get_check, list_issues, resolve_issue). Minor deviation: 'progress' is a single noun rather than verb_noun, and 'create_app' uses 'create' while others use 'add' or 'list', but the overall style is consistent and predictable.

Tool Count5/5

14 tools is well within the ideal range for a domain-specific server. Each tool addresses a necessary part of runbook management—creation, querying, updates, issue tracking, and coverage reporting—without bloat or redundant utilities.

Completeness4/5

The tool surface covers the full lifecycle of creating, reading, updating, and reporting on checks and issues. Missing features include deletion (e.g., remove_app, delete_check) and a dedicated get_issue tool, but these are not core to typical runbook workflows and can be worked around with existing tools.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 14 tool updates
    • First observedadd_check
    • First observedadd_issue
    • First observedadd_section
    • First observedcreate_app
    • First observededit_issue
    • First observedget_check
    • First observedimport_plan
    • First observedlist_apps
    • First observedlist_checks
    • First observedlist_issues
    • First observedprogress
    • First observedresolve_issue
    • First observedset_result
    • First observedupdate_check

Related MCP Connectors

Related MCP Servers

  • tapp

    aarwitz
    A
    license
    Not graded
    quality
    A
    maintenance
    Provides autonomous QA and a deterministic ship/no-ship verdict for iOS and web apps, enabling coding agents to explore, screenshot, and test apps via MCP tools.
    4,990 npm
    2
    MIT

  • uisight-mcp

    stefaniemorel38
    A
    license
    Not graded
    quality
    Not graded
    maintenance
    Runs live, URL-synced mobile and desktop sessions of a web or responsive UI and returns measured findings — contrast ratios, undersized touch targets, overflow, theme drift — as text with the offending selector attached, so an agent fixes the exact element instead of guessing from a screenshot. A shared panel lets a human pin a note and frame that the agent reads back, keeping both in front of the same screen.
    98 npm
    MIT

  • heimdall

    AntreasAntoniou
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables agents to author, validate, and execute browser/API test plans with parallel drivers, assertions, and captured evidence such as screenshots and network logs.
    1
    MIT
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources