google-search-console-mcp-server@2.1.2
VERIFIEDPublisher claims: "Google Search Console MCP server: 20 read tools, no write tools." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Started with a decoy GSC_ACCESS_TOKEN, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN; tool list observed. Tool calls with a real credential not tested.- Tested
- server startup with a tagged decoy in GSC_ACCESS_TOKEN, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN · MCP initialize and tools/list · every tool description, for hidden instructions · where the decoy credential went · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with a real credential
- Needs
- GSC_ACCESS_TOKEN, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.
Before you give it your token
- It will ask for
GSC_ACCESS_TOKENGSC_CLIENT_SECRETGSC_REFRESH_TOKENConfiguration, not credentials: GSC_CLIENT_ID, GSC_SITE_URL- Where it talks to
- getmcpads.com (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- what the tools do when called with a real credential
Connect it with a scoped credential, under the guard. It asks for GSC_ACCESS_TOKEN, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN and talks to getmcpads.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind.
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) on 2026-11-09 and scored it 87/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 51 s · 2 scenarios · 0 deviationsStatic findings
<summary><b>7 resources</b></summary> | URI | Contents | |---|---| | `gsc://manifest` | What this server exposes, and which tool to run first | | `gsc://metricsFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.No other findings across 10,152 lines in 11 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 @getmcpads/google-search-console-mcp-server@2.1.2 as of 7d ago. This is the package itself, not its dependencies.