mcp-google-search-console-crunchtools@0.5.2
VERIFIED· not startedPublisher claims: "Secure MCP server for Google Search Console analytics, sitemaps, and URL inspection" 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
GSC_CLIENT_SECRETGSC_CREDENTIALS_DIRGSC_OAUTH_REDIRECT_URIGSC_REFRESH_TOKENConfiguration, not credentials: GSC_BASE_URL, GSC_CLIENT_ID, GSC_RESOURCE_SERVER- 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 GSC_CLIENT_SECRET, GSC_CREDENTIALS_DIR, GSC_OAUTH_REDIRECT_URI, GSC_REFRESH_TOKEN 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-12 and scored it 81/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
encode_site_url("https://example.com; rm -rf /")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."http://user:pass@mcp-gsc:8017",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary><strong>Manual OAuth flow</strong></summary> ```bash export GSC_CLIENT_ID="your_client_id_here" export GSC_CLIENT_SECRET="your_client_secret_here" echoFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.encode_site_url("https://example.com; rm -rf /")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."https://bot:[email protected]/webmasters/v3/sites",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.-- podman run -i --rm \Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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-google-search-console-crunchtools@0.5.2 as of 2d ago. This is the package itself, not its dependencies.