gsc

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Security

Grade A, and why

gsc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

.mcp.json · 9 lines

What it actually says

{
  "gsc": {
    "//": "Custom Google Search Console MCP wrapper (mcp-gsc/server.py). ~150 lines, lives in this repo so we own the auth-handling code rather than trusting a third-party package. Exposes: list_sites, top_queries, top_pages, query_search, inspect_url. Uses the same ADC credentials as the ga4 server; webmasters.readonly scope must be granted (re-run gcloud auth application-default login with that scope if missing).",
    "command": "D:\\Quantcalc\\venv\\Scripts\\python.exe",
    "args": [
      "D:\\Quantcalc\\mcp-gsc\\server.py"
    ]
  }
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

Related

Other mcp servers, from other repositories