seo-stack-mcp@0.2.0
VERIFIED· not startedPublisher claims: "The complete open-source SEO data stack for AI agents — Google Search Console, GA4, Bing Webmaster Tools, Microsoft Clarity, AdSense, Google Keyword Planner and Open PageRank in one MCP server, with built-in analyst 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
BING_WEBMASTER_API_KEYCLARITY_API_TOKENGOOGLE_ADS_DEVELOPER_TOKENGOOGLE_APPLICATION_CREDENTIALSOPENPAGERANK_API_KEYSEO_STACK_OAUTH_CLIENTConfiguration, not credentials: ADSENSE_ACCOUNT_ID, ADSENSE_CURRENCY, BING_SITE_URL, CLARITY_CACHE_TTL, CLARITY_DAILY_LIMIT, CLARITY_WARNING_THRESHOLD, GA4_PROPERTY_ID, GOOGLE_ADS_LANGUAGE_ID, GOOGLE_ADS_LOCATION_ID, GSC_SITE_URL, OPENPAGERANK_CACHE_TTL, SEO_STACK_CONFIG_DIR, SEO_STACK_READONLY- Where it talks to
- no vendor host named in the codeAlso bing.com, clarity.ms, openpagerank.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 bing.com, clarity.ms, openpagerank.com as well as its own vendor. The guard injects BING_WEBMASTER_API_KEY, CLARITY_API_TOKEN, GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_APPLICATION_CREDENTIALS, OPENPAGERANK_API_KEY, SEO_STACK_OAUTH_CLIENT 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-18 and scored it 93/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
No findings across 5,397 lines in 32 files.
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 seo-stack-mcp@0.2.0 as of 29 min ago. This is the package itself, not its dependencies.