ghost-inspector-mcp

MCPcommunity
v0.4.1charliemtnezMITUpdated 6d agonpmGitHub

MCP server for the Ghost Inspector API — analyze, validate and safely update end-to-end browser tests from any MCP-capable agent

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 →
543Downloads/wk
6d agoLast update
Needs 1 credential before it runs
  • GHOST_INSPECTOR_API_KEYAPI keyrequired

    Your personal Ghost Inspector key, from Account Settings then API Access. Read fresh on every call, never written to disk, never echoed back.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorcharliemtnez
LicenseMIT
Version0.4.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface15 tools · 1 privileged
Security scan✓ Cleanv0.2.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

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

Tools

15 tools · 1 privileged
Statically extracted from the published packagev0.2.0 · 1mo ago

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.

gi_whoamiNo description published

This tool published no description. Forge does not invent one.

gi_inventoryNo description published

This tool published no description. Forge does not invent one.

gi_module_usageNo description published

This tool published no description. Forge does not invent one.

gi_stale_testsNo description published

This tool published no description. Forge does not invent one.

gi_get_testNo description published

This tool published no description. Forge does not invent one.

gi_test_resultNo description published

This tool published no description. Forge does not invent one.

gi_vacuous_testsNo description published

This tool published no description. Forge does not invent one.

gi_propose_repairNo description published

This tool published no description. Forge does not invent one.

gi_validate_testNo description published

This tool published no description. Forge does not invent one.

gi_update_testNo description published

This tool published no description. Forge does not invent one.

gi_move_suiteprivilegedNo description published

This tool published no description. Forge does not invent one.

gi_create_suiteNo description published

This tool published no description. Forge does not invent one.

gi_duplicate_testNo description published

This tool published no description. Forge does not invent one.

gi_run_testNo description published

This tool published no description. Forge does not invent one.

ghost-inspectorNo description published

This tool published no description. Forge does not invent one.

0 of 15 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.

About

MCP server for the Ghost Inspector API — analyze, validate and safely update end-to-end browser tests from any MCP-capable agent

Keywords
mcpmodel-context-protocolghost-inspectore2etestingbrowser-testingqa
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in browser automation & scraping