Browser-backed QA with evidence and fix-ready reports for coding agents.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
qa_ai_testNo description publishedThis tool published no description. Forge does not invent one.
qa_self_reviewNo description publishedThis tool published no description. Forge does not invent one.
qa_hire_testerNo description publishedThis tool published no description. Forge does not invent one.
qa_continueNo description publishedThis tool published no description. Forge does not invent one.
qa_request_runNo description publishedThis tool published no description. Forge does not invent one.
qa_get_run_statusNo description publishedThis tool published no description. Forge does not invent one.
qa_wait_for_runNo description publishedThis tool published no description. Forge does not invent one.
qa_get_run_reportNo description publishedThis tool published no description. Forge does not invent one.
qa_share_run_reportNo description publishedThis tool published no description. Forge does not invent one.
qa_request_human_testNo description publishedThis tool published no description. Forge does not invent one.
qa_get_human_test_statusNo description publishedThis tool published no description. Forge does not invent one.
qa_create_manual_sessionNo description publishedThis tool published no description. Forge does not invent one.
qa_start_manual_reviewNo description publishedThis tool published no description. Forge does not invent one.
qa_manual_review_guideNo description publishedThis tool published no description. Forge does not invent one.
qa_get_manual_sessionNo description publishedThis tool published no description. Forge does not invent one.
qa_get_manual_reportNo description publishedThis tool published no description. Forge does not invent one.
qa_get_manual_work_packetsNo description publishedThis tool published no description. Forge does not invent one.
qa_wait_for_manual_evidenceNo description publishedThis tool published no description. Forge does not invent one.
qa_wait_for_manual_feedbackNo description publishedThis tool published no description. Forge does not invent one.
qa_submit_manual_previewNo description publishedThis tool published no description. Forge does not invent one.
qa_submit_post_fix_reviewNo description publishedThis tool published no description. Forge does not invent one.
qa_run_feature_checkNo description publishedThis tool published no description. Forge does not invent one.
qa_check_workNo description publishedThis tool published no description. Forge does not invent one.
0 of 23 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Browser-backed QA with evidence and fix-ready reports for coding agents.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.