Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Google Search Console MCP

PYPI · SCALABLY-GSC-MCP · 2 COMPONENTS · SCANNED SEP 20

Read-only Google Search Console MCP: Search Analytics, sitemaps, URL inspection. 5 tools.

+6 this week 57 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 38 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1389 tokens (~277/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Google Search Console MCP server?

Google Search Console MCP runs locally as a PyPI package, launched with uvx scalably-gsc-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · scalably-gsc-mcp

# add to Claude Code
claude mcp add io-scalably-gsc-mcp -- uvx scalably-gsc-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "io-scalably-gsc-mcp": {
      "command": "uvx",
      "args": [
        "scalably-gsc-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-scalably-gsc-mcp": {
      "command": "uvx",
      "args": [
        "scalably-gsc-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add io-scalably-gsc-mcp -- uvx scalably-gsc-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-scalably-gsc-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "scalably-gsc-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-scalably-gsc-mcp --command uvx --arg scalably-gsc-mcp
# ~/.hermes/config.yaml
mcp_servers:
  io-scalably-gsc-mcp:
    command: "uvx"
    args: ["scalably-gsc-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-scalably-gsc-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "scalably-gsc-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add io-scalably-gsc-mcp -t stdio -c uvx -a scalably-gsc-mcp
// mcp.json
{
  "mcpServers": {
    "io-scalably-gsc-mcp": {
      "command": "uvx",
      "args": [
        "scalably-gsc-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −14
    • Malware scan: pass → unverified security
  • 16 Sept 26 +19
    • Malware scan: unverified → pass security
    • Stability: unverified → 0.27 functional
  • 13 Sept 26 −15
    • Malware scan: pass → unverified security
  • 12 Sept 26 +15
    • Malware scan: unverified → pass security
  • 8 Sept 26 51

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/scalably-gsc-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 38 packages
Packages resolved 38
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~1,389 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
gsc_batch_inspect_urls ~314

Inspect many URLs under a single Search Console property. Rate-limited. Respects Google's 600 QPM / 2,000 QPD per-site limits. Default pace of 8 QPS stays well under 600/minute with headroom. For large jobs (>2000 URLs), split across days or across multiple verified properties (e.g. per-subdomain). Args: urls: list of fully-qualified URLs under site_url. No dedup. site_url: the Search Console property. language_code: BCP-47, default "en-US". requests_per_second: pace. Max ~10 (600 QPM). Caller can lower on 429 pressure. continue_on_error: if True, collect per-URL errors instead of aborting. Returns: { "results": [{"url": str, "inspection": {...flattened...}} | {"url": str, "error": str}], "count": total, "errors": N, "skipped": 0 } Quota warning: This does NOT replace the Search Analytics API for bulk query analysis. If the intent is "which pages have most traffic", use gsc_query_search_analytics instead - 40,000 QPM per project vs 600/site here.

NameTypeReqDescription
continue_on_errorboolean
language_codestring
requests_per_secondnumber
site_urlstringyes
urlsarrayyes
NameTypeReqDescription
resultstringyes

No examples provided.

gsc_inspect_url ~218

Inspect a URL in the Google index. Flattened response. Checks index status, coverage state, canonical URLs, crawl info, AMP status, and rich results. Does NOT trigger a live crawl - checks Google's current index snapshot only. Args: inspection_url: fully-qualified URL to inspect (must be under the property). site_url: the Search Console property - "https://example.com/" or "sc-domain:example.com". language_code: IETF BCP-47, default "en-US". Quota: 2,000 requests/day/site + 600 requests/minute/site. Requires the SA to be a Full user on the property (Restricted users get 403 here). Returns a flat dict with top-level verdict, coverage_state, canonical info, plus optional `amp` and `rich_results` sub-objects. `_raw` has the full untouched payload.

NameTypeReqDescription
inspection_urlstringyes
language_codestring
site_urlstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

gsc_list_sitemaps ~182

List sitemaps on a site - or fetch one sitemap by feedpath. Args: site_url: the Search Console property. sitemap_index: optional - if set, list only the children of a sitemap-index URL (e.g. "https://example.com/sitemap_index.xml"). feedpath: optional - if set, returns the single sitemap entry at that URL instead of the list (absorbs the prior get_sitemap tool). Returns: {"sitemaps": [...], "count": N} or {"sitemap": {...}} if feedpath given. Each entry: {path, lastSubmitted, lastDownloaded, isPending, isSitemapsIndex, type, warnings, errors, contents}.

NameTypeReqDescription
feedpath
site_urlstringyes
sitemap_index
NameTypeReqDescription
resultstringyes

No examples provided.

gsc_list_sites ~79

List every verified Search Console property accessible to this service account. Returns: {"sites": [{siteUrl, permissionLevel}, ...], "count": N}. permissionLevel: siteOwner | siteFullUser | siteRestrictedUser | siteUnverifiedUser. Call this first. URL Inspection requires siteFullUser or siteOwner; restricted users cannot inspect.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

gsc_query_search_analytics ~596

Query Search Console traffic data - clicks, impressions, CTR, position. THE workhorse tool. Supports all six dimensions (incl. HOUR, April 2025), all six search types, full filter compose, pagination, and auto-pagination. Args: site_url: "https://example.com/" (URL-prefix) or "sc-domain:example.com" (domain). start_date / end_date: YYYY-MM-DD (Pacific Time). 16-month retention hard cap. dimensions: list of {date, query, page, country, device, searchAppearance, HOUR}. HOUR requires data_state='hourly_all'. searchAppearance cannot be combined with other dimensions in one query - query it alone and join client-side. search_type: web (default) | image | video | news | discover | googleNews. filters: flat list [{dimension, operator, expression}]. Operators: equals, contains, notEquals, notContains, includingRegex, excludingRegex. filter_groups: advanced - pass raw dimensionFilterGroups if you need OR logic. Mutually exclusive with `filters`. aggregation_type: auto (default) | byPage | byProperty | byNewsShowcasePanel. data_state: final (default, ~2-3d lag) | all (fresh, includes unfinalized) | hourly_all (~10d history with HOUR dimension). row_limit: per-call cap, 1–25000 (API hard cap). start_row: 0-based offset for single-page paging. max_rows: if set (up to 1M), auto-paginate until exhausted or max_rows hit. Response: {rows, row_count, response_aggregation_type, first_incomplete_date?, first_incomplete_hour?, metadata}. Use first_incomplete_date to distinguish 'data still cooking' from 'data is final' when data_state != 'final'. Gotchas: - 16-month retention. start_date older than 16 months returns empty. - Anonymized queries (fewer than ~a dozen users over 2-3 months) drop from the 'query' dimension but count in totals - page-level data is more complete. - Aggregation shift: with a page filter, totals aggregate byPage (inflates clicks vs property-level). Set aggregation_type explicitly when comparing. - s…

NameTypeReqDescription
aggregation_type
data_state
dimensions
end_datestringyes
filter_groups
filters
max_rows
row_limitinteger
search_type
site_urlstringyes
start_datestringyes
start_rowinteger
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the Google Search Console MCP server?

Google Search Console MCP is listed in the public MCP registry as io.scalably/gsc-mcp. Read-only Google Search Console MCP: Search Analytics, sitemaps, URL inspection. 5 tools. This page covers its PyPI package (scalably-gsc-mcp).

Is the Google Search Console MCP server safe to use?

Google Search Console MCP scores 57 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Google Search Console MCP server expose?

Google Search Console MCP exposes 5 tools: gsc_list_sites, gsc_query_search_analytics, gsc_list_sitemaps, gsc_inspect_url, gsc_batch_inspect_urls. Their descriptions and schemas cost roughly 1,389 tokens of context every time the server is loaded.

Is the Google Search Console MCP server still maintained?

Google Search Console MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Google Search Console MCP server under?

Google Search Console MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.