mcp-gsc

Google Search Console Insights with Claude AI for SEOs

Runssource: GitHubPythonMITcommit d49eea9e5efb

Python, MIT licensed. The project labels itself: claude, google search console, mcp server and seo.

mcp-gsc runs. An Argusic agent installed it in 2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 52 automated tests pass, the server module imports cleanly, and the SSE transport starts and responds to MCP handshake on port 3001.

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
2
last tested
stars
2,243
forks
289
open issues
8
watchers
22
size
2 MB
created
last push

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.

Time lost to each failure while testing mcp-gsc, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Externally managed Python environment prevented system pip install1 minute
  • pytest not installed in venv1 minute
Install time
2 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
/tmp/venv/bin/pytest test_gsc_server.py -v exited 0 with 52 passed; server launched with MCP_TRANSPORT=sse and curl to /sse returned 200 with the expected SSE endpoint event
Model tokens used
30,400
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

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Has get_capabilities: True
Has list_properties: True
Has get_search_analytics: True
MCP object type: mcp.server.fastmcp.server.FastMCP
Number of registered tools (indirect): N/A
Everything works. Let me compile the final result.
exec
/bin/sh -lc 'cd /work/repo && cat /tmp/venv/bin/python3 /work/repo/gsc_server.py > /dev/null 2>&1 &…
 succeeded in 0ms:
Server parse OK
tokens used
30,400

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

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 2 minutes.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 9 claude projects Argusic has installed and timed, mcp-gsc was the 5th fastest to reach a running state, and 5 of 9 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 2 minutes after the clone.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.03
Argusic Runner1/3Runs with mocks92.000.03

Topics (from GitHub)

claudegoogle-search-consolemcp-serverseo

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/mcp-gsc.svg)](https://argusic.com/subject/mcp-gsc)

Questions

Does mcp-gsc run?
Yes. mcp-gsc runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 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. 2 attempts are 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?
2 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?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does mcp-gsc compare with the alternatives?
Of the 9 claude projects Argusic has installed and timed, mcp-gsc was the 5th fastest to reach a running state, and 5 of 9 reached one at all.
Where is the evidence for mcp-gsc?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion