scalably-gsc-mcp@1.0.1
VERIFIED· not startedPublisher claims: "Read-only MCP server for Google Search Console: sites, Search Analytics with auto-pagination and hourly data, sitemaps, URL inspection and batch 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
GOOGLE_APPLICATION_CREDENTIALSGSC_TEST_ACCESS_TOKENConfiguration, not credentials: GSC_LOG_LEVEL, GSC_RETRY_BASE_SECONDS, GSC_SEARCHCONSOLE_BASE, GSC_WEBMASTERS_BASE- 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 GOOGLE_APPLICATION_CREDENTIALS, GSC_TEST_ACCESS_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-16 and scored it 89/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
- run: npx -y @anthropic-ai/[email protected] validate manifest.jsonFix: Pin versions and sources; vendor anything fetched at install time.TRACKED = subprocess.run(["git", "ls-files", "-z"], cwd=REPO, check=True, capture_output=True).stdout.decode().split("\0")Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.- run: npx -y @anthropic-ai/[email protected] validate manifest.jsonFix: Pin versions and sources; vendor anything fetched at install time.- run: npx -y @anthropic-ai/[email protected] pack . "${GITHUB_REPOSITORY#*/}.mcpb"Fix: Pin versions and sources; vendor anything fetched at install time.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 scalably-gsc-mcp@1.0.1 as of 48 min ago. This is the package itself, not its dependencies.