MCP Google Search Console
PYPI · MCP-GOOGLE-SEARCH-CONSOLE-CRUNCHTOOLS
Secure MCP server for Google Search Console analytics, sitemaps, and URL inspection
Available components
Last scanned (9 hours ago)
Scores higher than 72% 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
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to crunchtools/mcp-google-search-console). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 728 tokens (~72/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_site_tool" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 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
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
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −20
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.63 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: 0.83 → pass security
- 16 Oct 26 +13
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.83 functional
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/mcp-google-search-console-crunchtools@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | crunchtools/mcp-google-search-console |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/crunchtools/mcp-google-search-console/.github/workflows/publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 1015678383 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f0037518a97a6383d4eeb41a317321584556e4c731413b24eeeade6ef61a5429 |
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 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 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 →
add_site_tool Add Site Tool ~40
Add a site to Search Console.
| Name | Type | Req | Description |
|---|---|---|---|
| site_url | string | yes | Site URL (e.g., "https://example.com/") or domain property |
Structured output declared, but exposes no named fields.
No examples provided.
delete_site_tool Delete Site Tool ~28
Remove a site from Search Console.
| Name | Type | Req | Description |
|---|---|---|---|
| site_url | string | yes | Site URL to remove |
Structured output declared, but exposes no named fields.
No examples provided.
delete_sitemap_tool Delete Sitemap Tool ~45
Remove a sitemap from Search Console.
| Name | Type | Req | Description |
|---|---|---|---|
| feedpath | string | yes | Full URL of the sitemap to delete |
| site_url | string | yes | Site URL or domain property |
Structured output declared, but exposes no named fields.
No examples provided.
get_site_tool Get Site Tool ~54
Get details for a specific Search Console property.
| Name | Type | Req | Description |
|---|---|---|---|
| site_url | string | yes | Site URL (e.g., "https://example.com/") or domain property (e.g., "sc-domain:example.com") |
Structured output declared, but exposes no named fields.
No examples provided.
get_sitemap_tool Get Sitemap Tool ~55
Get details for a specific sitemap.
| Name | Type | Req | Description |
|---|---|---|---|
| feedpath | string | yes | Full URL of the sitemap (e.g., "https://example.com/sitemap.xml") |
| site_url | string | yes | Site URL or domain property |
Structured output declared, but exposes no named fields.
No examples provided.
inspect_url_tool Inspect Url Tool ~103
Inspect a URL's index status in Google Search. Returns detailed information about how Google sees a URL including index coverage, crawl status, mobile usability, and rich results.
| Name | Type | Req | Description |
|---|---|---|---|
| inspection_url | string | yes | The fully-qualified URL to inspect (e.g., "https://example.com/page") |
| language_code | string | – | Language code for localized results (default: en-US) |
| site_url | string | yes | The Search Console property this URL belongs to |
Structured output declared, but exposes no named fields.
No examples provided.
list_sitemaps_tool List Sitemaps Tool ~34
List all sitemaps submitted for a site.
| Name | Type | Req | Description |
|---|---|---|---|
| site_url | string | yes | Site URL or domain property |
Structured output declared, but exposes no named fields.
No examples provided.
list_sites_tool List Sites Tool ~20
List all Search Console properties accessible by the authenticated user.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
query_search_analytics_tool Query Search Analytics Tool ~254
Query search traffic data with filters and dimensions. Returns clicks, impressions, CTR, and average position grouped by the requested dimensions. Use this to analyze search performance for specific pages, queries, countries, devices, or date ranges.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregation_type | string | – | How to aggregate results (auto, byPage, byProperty). Default: auto |
| data_state | string | – | Data freshness (final, all). Default: final |
| dimension_filter_groups | – | – | Filter groups to narrow results |
| dimensions | – | – | Dimensions to group by (date, query, page, country, device, searchAppearance). Multiple allowed. |
| end_date | string | yes | End date in YYYY-MM-DD format |
| row_limit | integer | – | Maximum rows to return, 1-25000 (default: 1000) |
| search_type | string | – | Search type filter (web, image, video, news, googleNews, discover). Default: web |
| site_url | string | yes | Site URL or domain property |
| start_date | string | yes | Start date in YYYY-MM-DD format |
| start_row | integer | – | Zero-based row offset for pagination (default: 0) |
Structured output declared, but exposes no named fields.
No examples provided.
submit_sitemap_tool Submit Sitemap Tool ~56
Submit a sitemap for crawling.
| Name | Type | Req | Description |
|---|---|---|---|
| feedpath | string | yes | Full URL of the sitemap to submit (e.g., "https://example.com/sitemap.xml") |
| site_url | string | yes | Site URL or domain property |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the MCP Google Search Console server?
MCP Google Search Console runs locally as a PyPI package, launched with uvx mcp-google-search-console-crunchtools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-google-search-console-crunchtools
claude mcp add crunchtools-google-search-console -- uvx mcp-google-search-console-crunchtools
What is the MCP Google Search Console server?
MCP Google Search Console is listed in the public MCP registry as io.github.crunchtools/google-search-console. Secure MCP server for Google Search Console analytics, sitemaps, and URL inspection. This page covers its PyPI package (mcp-google-search-console-crunchtools).
Is the MCP Google Search Console server safe to use?
MCP Google Search Console scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 MCP Google Search Console server expose?
MCP Google Search Console exposes 10 tools: list_sites_tool, get_site_tool, add_site_tool, delete_site_tool, query_search_analytics_tool, and 5 more. Their descriptions and schemas cost roughly 689 tokens of context every time the server is loaded.
Is the MCP Google Search Console server still maintained?
MCP Google Search Console 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 MCP Google Search Console server under?
MCP Google Search Console declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.