mcp-gsc
Google Search Console Insights with Claude AI for SEOs
Runs with mockssource: GitHubPythonMITcommit d49eea9e5efb
Python, MIT licensed. The project labels itself: claude, google search console, mcp server and seo.
mcp-gsc runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
All 52 unit tests pass with mocked GSC API. The server loads, registers 21 MCP tools, completes MCP initialization handshake, responds to tools/list and tools/call via stdio transport, and serves 200 on the SSE endpoint.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- under a minute
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pytest test_gsc_server.py -v: 52 passed, 0 failed (exit code 0); MCP stdio handshake returned tools/list with 21 tools; SSE /sse returned HTTP 200; tools/call get_capabilities returned structured JSON output
- Model tokens used
- 30,825
- Exact commit tested
- d49eea9e5efb
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Now I have all the data for the final report. Let me enumerate the results: **Install**: Created a virtual environment, installed all dependencies from `requirements.txt` — no… **Tests**: `pytest test_gsc_server.py -v` → 52 passed in ~1.25s. **App launch (stdio)**: MCP handshake completed, `tools/list` returned 21 tools, `tools/call get_ca… **App launch (SSE)**: Server bound to `127.0.0.1:13001`, `/sse` returned `200 OK` with `event: endp… tokens used 30,825 Now I have all the data for the final report. Let me enumerate the results: **Install**: Created a virtual environment, installed all dependencies from `requirements.txt` — no… **Tests**: `pytest test_gsc_server.py -v` → 52 passed in ~1.25s. **App launch (stdio)**: MCP handshake completed, `tools/list` returned 21 tools, `tools/call get_ca… **App launch (SSE)**: Server bound to `127.0.0.1:13001`, `/sse` returned `200 OK` with `event: endp…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 0.5 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.03 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcp-gsc)Questions
- Does mcp-gsc run?
- mcp-gsc runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test mcp-gsc?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d49eea9e5efb. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mcp-gsc?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mcp-gsc take to install?
- 0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does mcp-gsc need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mcp-gsc?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for mcp-gsc?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.