Google Search Console MCP
PYPI · GOOGLE-SEARCH-CONSOLE-MCP
Google Search Console MCP: search performance analytics, rankings, sitemaps, and indexing health.
Available components
Last scanned (3 hours ago)
Scores higher than 56% of PyPI servers
Category Marketing and SEO
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 build step with no custom scripting around it. View diagnostics → Pass
- 2 of 50 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1079 tokens (~63/item across 17 items; 12 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 (8% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 55
First indexed and scored.
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 5 Nov 2026 · Analysed pypi/google-search-console-mcp@0.10.10
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 50 packages
| Packages resolved | 50 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_for_updates ~24
Check PyPI for newer versions of this MCP server and get upgrade instructions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_sitemap ~50
Delete a sitemap from Google Search Console. Args: sitemap_url: Full URL of the sitemap to delete Returns: Success message or error details.
| Name | Type | Req | Description |
|---|---|---|---|
| sitemap_url | string | yes | – |
No output schema declared.
No examples provided.
get_search_analytics ~301
Retrieve Google Search Console search analytics data. Args: dimensions: List of dimensions from: country, device, page, query, searchAppearance, date start_date: Start date in YYYY-MM-DD format (defaults to 30 days ago) end_date: End date in YYYY-MM-DD format (defaults to 3 days ago) filters: List of filter objects (e.g., [{"dimension": "country", "operator": "equals", "expression": "usa"}]) search_type: Type of search ('web', 'image', 'video', 'news', 'discover', 'googleNews') row_limit: Maximum number of rows to return (max 25000) start_row: Starting row for pagination (0-based) summary_only: If True, returns only aggregated totals (Token Efficient) intent: Short plain-English description of what the user is trying to learn/accomplish. E.g. "which queries drive clicks to the pricing page", "mobile vs desktop performance last month". Returns: Dictionary containing search analytics data with clicks, impressions, ctr, and position metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | array | – | – |
| end_date | – | – | – |
| filters | – | – | – |
| intent | string | – | – |
| row_limit | integer | – | – |
| search_type | string | – | – |
| start_date | – | – | – |
| start_row | integer | – | – |
| summary_only | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_sitemaps ~35
Get all sitemaps for the configured site. Returns: List of sitemaps with their status and details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_available_dimensions ~33
List all available GSC dimensions with their descriptions. Returns: List of dimension objects with api_name and description.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_available_metrics ~33
List all available GSC metrics with their descriptions. Returns: List of metric objects with api_name and description.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_gsc_sites ~32
List all sites verified in Google Search Console. Returns: List of verified sites with their permission levels.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sites ~37
List all sites verified in Google Search Console (alias for list_gsc_sites). Returns: List of verified sites with their permission levels.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
setup_gsc_access ~78
Interactively fix a broken Google Search Console MCP setup (missing or wrong credentials path, missing GSC_SITE_URL, invalid key, or missing property access) by asking the user for the needed value through the client, then re-initializing without a restart. Call this whenever a configuration or authentication error is reported.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
skill_read ~73
Fetch the full content of one analytical skill (playbook) for Google Search Console. Args: skill_id: The skill id from skills_list (e.g., "brand_visibility.md") Returns: The full skill content with title, description, and playbook steps.
| Name | Type | Req | Description |
|---|---|---|---|
| skill_id | string | yes | – |
No output schema declared.
No examples provided.
skills_list ~50
List available analytical skills (playbooks) for Google Search Console. Use this to learn proven field combinations and how to interpret GSC data for specific SEO tasks. Fetch the full playbook with skill_read.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_sitemap ~50
Submit a sitemap to Google Search Console. Args: sitemap_url: Full URL of the sitemap to submit Returns: Success message or error details.
| Name | Type | Req | Description |
|---|---|---|---|
| sitemap_url | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Google Search Console MCP server?
Google Search Console MCP runs locally as a PyPI package, launched with uvx google-search-console-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 · google-search-console-mcp
claude mcp add surendranb-google-search-console-mcp -- uvx google-search-console-mcp
What is the Google Search Console MCP server?
Google Search Console MCP is listed in the public MCP registry as io.github.surendranb/google-search-console-mcp. Google Search Console MCP: search performance analytics, rankings, sitemaps, and indexing health. This page covers its PyPI package (google-search-console-mcp).
Is the Google Search Console MCP server safe to use?
Google Search Console MCP scores 55 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 12 tools: list_gsc_sites, list_sites, list_available_dimensions, list_available_metrics, skills_list, and 7 more. Their descriptions and schemas cost roughly 796 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 5 November 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.