io.github.SyncTekLLC/ghostqa

MCPcommunity
v0.2.2io.github.SyncTekLLCUnknownUpdated 7mo agoGitHub

AI personas navigate your web app in real browsers, find bugs and UX issues. No scripts needed.

AI personas walk your app so real users don't trip. SpecterQA sends AI personas through your application — they look at the screen, decide what to do, and interact like real humans. No test scripts. No selectors. You describe personas and journeys in YAML, and SpecterQA handles the rest. Traditional E2E tests are brittle. You write selectors, they break. You maintain scripts, they rot. SpecterQA…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2Forks
7mo agoLast update
Package
Authorio.github.SyncTekLLC
LicenseUnknown
Version0.2.2
Sourcemcp-registry
Trust Status
F
10/100Untrusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
—Prompt-injection scan · not run+0/30
→ Our scan didn't complete — a retry is queued. Nothing to fix on your side.
—Obfuscation / exfil scan · not run+0/20
→ Our scan didn't complete — a retry is queued. Nothing to fix on your side.
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanScan failedvunknown · 1mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Source never read1mo ago

This entry has been scanned, but the run carries no source-extraction result — either it predates tool-surface extraction or it failed before reaching that stage. A rescan is what would fill this in; the blank says nothing about the package.

About

AI personas walk your app so real users don't trip. SpecterQA sends AI personas through your application — they look at the screen, decide what to do, and interact like real humans. No test scripts. No selectors. You describe personas and journeys in YAML, and SpecterQA handles the rest. Traditional E2E tests are brittle. You write selectors, they break. You maintain scripts, they rot. SpecterQA takes a different approach: AI vision models look at your actual UI and navigate it the way a person…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.