mcp-seo-audit@2.0.2
VERIFIED· not startedPublisher claims: "SEO audit & indexing MCP server — Google Search Console, Indexing API, Core Web Vitals, and site analysis tools" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
CRUX_API_KEYGOOGLE_API_KEYGSC_CREDENTIALS_PATHGSC_OAUTH_CLIENT_SECRETS_FILEGSC_SKIP_OAUTHPAGESPEED_API_KEYConfiguration, not credentials: CHROME_PATH, GSC_DATA_STATE, LIGHTHOUSE_BINARY, LIGHTHOUSE_CHROME_PATH, LIGHTHOUSE_NO_SANDBOX, SEO_AUDIT_ALLOW_NPX_LIGHTHOUSE, SEO_AUDIT_ALLOW_PRIVATE_URLS, SEO_AUDIT_ENABLE_WRITE_TOOLS, SEO_AUDIT_MAX_CRAWL_PAGES, SEO_AUDIT_MAX_FETCH_BYTES, SEO_AUDIT_MAX_REDIRECTS, SEO_AUDIT_MAX_SITEMAP_URLS- Where it talks to
- no vendor host named in the codeAlso google.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names google.com as well as its own vendor. The guard injects CRUX_API_KEY, GOOGLE_API_KEY, GSC_CREDENTIALS_PATH, GSC_OAUTH_CLIENT_SECRETS_FILE, GSC_SKIP_OAUTH, PAGESPEED_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-09 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
"or set SEO_AUDIT_ALLOW_NPX_LIGHTHOUSE=true to allow npx to download/run Lighthouse."Fix: Pin versions and sources; vendor anything fetched at install time.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mcp-seo-audit@2.0.2 as of 5d ago. This is the package itself, not its dependencies.