Google Search Console MCP (pijusz)
Capped at 70: no passing tool call yet; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm mcp-gsc 0.4.1 (MIT; repo pijusz/mcp-gsc). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 21 tools (21 annotated by the server: 20 read-only, 1 destructive). Real calls: 0 of 3 real function calls passed. Calls need Google Search Console credentials (GOOGLE_GSC_CREDENTIALS_PATH). Core tools not tested: 70 cap.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): fail. 0 of 3 real function calls passed. Calls need Google Search Console credentials (GOOGLE_GSC_CREDENTIALS_PATH). Evidence: local test run, Nov 13, 2026 UTC.
Transport (tested 2026-11-13 UTC): stdio
Token cost (estimate): approx. 3583 tokens, cl100k estimate (21 tools, measured 2026-11-13 UTC, version 0.4.1). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 7 read, 0 write (state-changing), 14 unclassified · Auth: API key · Rate limit: unknown · Pricing unit: unknown
Auth: API key. Rate limit: unknown. Pricing unit: unknown.
batch_inspect_urls— readcannibalization— unclassifiedcompare_periods— unclassifiedcontent_decay— unclassifiedctr_anomalies— unclassifieddevice_country_breakdown— unclassifiedexport_csv— unclassifiedget_property_details— readget_sitemap— readindexing_coverage— unclassifiedinspect_url— readlist_properties— readlist_sitemaps— readopportunity_finder— unclassifiedperformance_overview— unclassifiedposition_tracking— unclassifiedquick_wins— unclassifiedsearch_analytics— readsitemap_health— unclassifiedtop_movers— unclassifiedweekly_seo_report— unclassified
listing-flags calls_need_key or auth_kind
Score 70/100 · Tools 21 · Token cost approx. 3,583 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 0.4.1 · Package mcp-gsc · Repo pijusz/mcp-gsc
Summary: Google Search Console MCP (pijusz) completed an MCP handshake without credentials and exposed 21 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 21
- Context cost
- approx. 3583 tokens, cl100k estimate (21 tools, measured 2026-11-13 UTC, version 0.4.1; an estimate) ranking · add up your servers' context cost
- API key
- Connects without a key; tool calls need one
- Tested
- 2026-11-13 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install mcp-gsc (Node 20, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 21 tools listed in 5.5s. |
| maintenance | pass | 25 | Repo pushed 21 days before test; 3 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 3583 tokens, cl100k estimate for 21 tools · about 44% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-13 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 21 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-13 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
a5fa8d02b057: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "mcp-gsc",
"version": "0.4.1",
"registry": "npm",
"status": "working",
"tested": "2026-11-13",
"tools_count": 21,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install mcp-gsc` (Node 20, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 21 tools listed in 5.5s."
],
"maintenance": [
"pass",
25,
"Repo pushed 21 days before test; 3 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y mcp-gsc
Pin the version we tested
npx -y mcp-gsc@0.4.1
tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"google-search-console-mcp-pijusz": {
"command": "npx",
"args": [
"-y",
"mcp-gsc@0.4.1"
]
}
}
}Tools listed
list_properties, get_property_details, search_analytics, list_sitemaps, get_sitemap, inspect_url, batch_inspect_urls, export_csv, performance_overview, compare_periods, top_movers, device_country_breakdown, quick_wins, cannibalization, opportunity_finder, position_tracking, ctr_anomalies, content_decay, weekly_seo_report, indexing_coverage, sitemap_health
Quick config
{
"mcpServers": {
"google-search-console-mcp-pijusz": {
"command": "npx",
"args": [
"-y",
"mcp-gsc"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install mcp-gsc(Node 20). This is the exact command we ran on 2026-11-13 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (21 in our test).
{
"mcpServers": {
"google-search-console-mcp-pijusz": {
"command": "npx",
"args": [
"-y",
"mcp-gsc"
]
}
}
}Test history
- 2026-11-13 UTC: New
FAQ
Is Google Search Console MCP (pijusz) deprecated?
No. mcp-gsc was not deprecated or archived when we last tested it on 2026-11-13 UTC.
What replaces Google Search Console MCP (pijusz)?
Nothing; Google Search Console MCP (pijusz) is not deprecated as of 2026-11-13 UTC.
Does Google Search Console MCP (pijusz) need an API key?
It connects and lists 21 tools without a key, but its tool calls need one.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.