AminForou/mcp-gsc

Review signals: 59 known vulnerability.

Reviewed as expected for a test run: attempted writes that failed, so nothing was written.

OSV reports a known vulnerability in this dependency version. 10 distinct locations. 59 findings.

OSV scanned supported lockfiles; unpinned dependencies and unsupported formats are outside this check.

A short run cannot establish that code is safe.

Connections show IP addresses; proxies can hide the final hostname.

Tracing covers dispatched commands and their children, not the whole OS; guest root can interfere with tracing.

Full safety evidence →

• get_capabilities lists all tools for the full list of 20 tools: Real input produced the expected result: list_properties: List all GSC sites/properties you have access to

  Source: *Ask your AI assistant to "call get_capabilities" for the full list of all 20 tools.*

  Input: {"tool": "get_capabilities", "arguments": {}}

  Expected: tool list including list_properties

  Command: <guest-path> <guest-path> tools/call {"tool": "get_capabilities", "arguments": {}}

  Observed: list_properties: List all GSC sites/properties you have access to (start here)\n - get_site_details: Get verification and ownership details for a site\n\nAnalytics & Reporting:\n - get_search_analytics: Top queries and pages with clicks, impressions, CTR, position\n - get_performance_overview: Summary of site performance for a time period\n - compare_search_periods: Compare performance between two time periods\n - get_search_by_page_query: Search terms driving traffic to a specific page\n - get_advanced_search_analytics: Advanced filtering by country, device, query, page\n\nURL Inspectio

Examples

• Offline test suite for the server (documented in CLAUDE.md): command completed successfully

  Source: CLAUDE.md

  Input: test_gsc_server.py

  Expected: all tests pass

  Command: <guest-path> test_gsc_server.py -v

  Observed: pass/workspace/.venv/lib/python3.11/site-packages/google/api_core/_python_version_support.py:254: FutureWarning: You are using a Python version (3.11.17) which Google will stop supporting in new releases of google.api_core once it reaches its end of life (2027-10-24). Please upgrade to the latest Python version, or at least Python 3.12, to continue receiving updates for google.api_core past that date. warnings.warn(message, FutureWarning) -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html ======================== 52 passed, 1 warning in 4.84s =========================

Local or hosted: both

Run the Google Search Console MCP server (gsc_server.py) over stdio and call its tools, e.g. get_capabilities (works) and list_properties (needs Google credentials).

cd <guest-path> && pwd && ls -la && git status 2>&1 | head -3; id -u; python3 --version; cat README.md 2>/dev/null | head -150
cd <guest-path> && sed -n '150,400p' README.md | cut -c1-400; cat .python-version pyproject.toml | head -60; ls .coldpass <guest-path> 2>&1
cd <guest-path> && which uv uvx; uv --version 2>&1; cat requirements.txt; cat .mcp.json; cat mcp.json; grep -n "def get_capabilities\|GSC_SKIP_OAUTH\|GSC_CREDENTIALS_PATH\|def main\|mcp.run\|FastMCP(" gsc_server.py | head -30
cd <guest-path> && uv venv .venv 2>&1 | tail -3 && uv pip install -p .venv/bin/python -r requirements.txt 2>&1 | tail -5
cd <guest-path> && sed -n 250,300p gsc_server.py; sed -n 1,40p <guest-path> | cut -c1-200
cd <guest-path> && sed -n 95,175p gsc_server.py | cut -c1-180
cd <guest-path> && grep -c 'Ask your AI assistant to \\"call get_capabilities\\" for the full list of all 20 tools' README.md; grep -c 'Set to `\\"true\\"` to force service account auth and skip OAuth entirely' README.md; grep -c 'list_properties: List all GSC sites' gsc_server.py; cat > .coldpass/probe.json <<'EOF'
{"kind":"mcp","argv":["<guest-path>","<guest-path>"],"cwd":"<guest-path>","env":{"GSC_SKIP_OAUTH":"true"},"tool":"get_capabilities","arguments":{},"expected_text":"Not authenticated"}
EOF
cat > .coldpass/claims.json <<'EOF'
[{"kind":"claim","claim":"get_capabilities lists all tools for the full list of 20 tools","source":"*Ask your AI assistant to \"call get_capabilities\" for the full list of all 20 tools.*","input":"get_capabilities with no arguments","expected":"tool list including list_properties","probe_kind":"mcp","argv":["<guest-path>","<guest-path>"],"tool":"get_capabilities","arguments":{},"expected_text":"list_properties: List all GSC sites/properties you have access to","env":{"GSC_SKIP_OAUTH":"true"},"cwd":"<guest-path>"}]
EOF
python3 -m json.tool .coldpass/probe.json >/dev/null && python3 -m json.tool .coldpass/claims.json >/dev/null && echo OK
cd <guest-path> && python3 -I -c "
import json
t=open('README.md',encoding='utf-8').read()
c=json.load(open('.coldpass/claims.json'))[0]
print(c['source'] in t)
print('Set to \`\"true\"\` to force' in t)
"
cd <guest-path> && grep -n -i "pytest\|test_\|cron\|schedul\|--once\|webhook" README.md CLAUDE.md CHANGELOG.md | head; grep -n -i "schedul\|cron\|while True\|--once" gsc_server.py | head -5; cat CLAUDE.md | head -40 | cut -c1-200
cd <guest-path> && uv pip install -p .venv/bin/python pytest 2>&1 | tail -2 && timeout 600 .venv/bin/python -m pytest test_gsc_server.py -q 2>&1 | tail -8
cd <guest-path> && cat > .coldpass/examples.json <<'EOF'
[{"kind":"example","claim":"Offline test suite for the server (documented in CLAUDE.md)","source":"CLAUDE.md","input":"test_gsc_server.py","expected":"all tests pass","argv":["<guest-path>","test_gsc_server.py","-v"],"cwd":"<guest-path>","env":{"GSC_SKIP_OAUTH":"true"},"expected_text":"52 passed"}]
EOF
cat > .coldpass/cycles.json <<'EOF'
{"detected":false,"reason":"Entry points inspected (gsc_server.py main(), README, CLAUDE.md, pyproject.toml scripts). The server is a request-driven MCP stdio/SSE server with no scheduler, cron, loop, --once or webhook trigger; it only runs when an MCP client calls a tool.","checks":[]}
EOF
python3 -I -m json.tool .coldpass/examples.json >/dev/null && python3 -I -m json.tool .coldpass/cycles.json >/dev/null && echo OK; <env-var>=<guest-path> timeout 900 python3 -I <guest-path> --validate --replay 2>&1 | tail -40
cd <guest-path> && mkdir -p .coldpass && cat > .coldpass/report.json <<'EOF'
{"outcome":"needs_credentials","fault_owner":"prerequisite","operation":"Run the Google Search Console MCP server (gsc_server.py) over stdio and call its tools, e.g. get_capabilities (works) and list_properties (needs Google credentials).","operation_scope":"Local clone install per README Step 2 Option B on Python 3.11+ (VM has uv 0.13.5 and CPython 3.11.17 in the venv). Real GSC data calls need a Google OAuth client_secrets.json or a service account JSON, neither of which exists in this VM. Tested with GSC_SKIP_OAUTH=true so no browser login is attempted.","steps":["curl/uv already present; uv venv .venv","uv pip install -r requirements.txt (README Option B, clone path)","GSC_SKIP_OAUTH=true .venv/bin/python gsc_server.py (MCP stdio) and tools/call get_capabilities -> returned tool list and 'Not authenticated' auth status","uv pip install pytest, then .venv/bin/pytest test_gsc_server.py -v (CLAUDE.md) -> 52 passed"],"deviations":["Used 'uv pip install -p .venv/bin/python' to point uv at the venv explicitly; otherwise the README commands are unchanged.","Installed pytest into the venv because CLAUDE.md's documented test command needs it; it is not in requirements.txt.","Did not run list_properties or any analytics tool: no Google credentials available in the VM (needs_credentials). Nothing was installed or downloaded beyond the Python dependencies; no browser was used.","README uvx path (uvx mcp-search-console) not run; it fetches the published package instead of the checked-out source."],"stuck_step":"README 'Step 1 — Set Up Google API Credentials' (OAuth client_secrets.json or service account JSON) before any real Search Console call such as list_properties.","main_blocker":"No Google Search Console credentials (OAuth client secrets or service account key) are available in this disposable VM.","plain_failure":"The server starts and its tools respond, and the offline test suite passes (52 tests). But the tools that read real Search Console data cannot run until someone supplies a Google login file or service-account key. The check of get_capabilities correctly reports 'Not authenticated', so the auth path works as documented.","suggested_fix":"Provide a GSC_OAUTH_CLIENT_SECRETS_FILE (with a browser login) or a GSC_CREDENTIALS_PATH service account key with GSC_SKIP_OAUTH=true, then re-run list_properties against a verified property."}
EOF
python3 -I -m json.tool .coldpass/report.json >/dev/null && echo REPORT_OK; ps aux | grep -c "[g]sc_server"; <env-var>=<guest-path> python3 -I <guest-path> --validate --replay 2>&1 | python3 -c "import sys,json; d=json.loads(sys.stdin.read()); print(d['valid'], d['problems'], d['replay']['status'])"
ps -eo pid,ppid,etime,args | grep "[g]sc_server"