# Google Search Console MCP (npm · @renzo.johnson/google-search-console-mcp)

Search Console MCP server: search analytics, URL inspection, sitemaps and the Indexing API.

- Trust score: 65/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@renzo.johnson/google-search-console-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-renzojohnson-google-search-console-mcp/renzo-johnson-google-search-console-mcp.md), [page](https://verifymcp.io/servers/com-renzojohnson-google-search-console-mcp/renzo-johnson-google-search-console-mcp)

## Channel facts

- Registry: `npm`
- Package: `@renzo.johnson/google-search-console-mcp`
- Version: `26.11.14`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 684 tokens (~76/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### How do I install the Google Search Console MCP server?

Google Search Console MCP runs locally as an npm package, launched with npx -y @renzo.johnson/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.

### Claude

```bash
claude mcp add com-renzojohnson-google-search-console-mcp -- npx -y @renzo.johnson/google-search-console-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-renzojohnson-google-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-search-console-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-renzojohnson-google-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-search-console-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-renzojohnson-google-search-console-mcp -- npx -y @renzo.johnson/google-search-console-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-renzojohnson-google-search-console-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@renzo.johnson/google-search-console-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-renzojohnson-google-search-console-mcp --command npx --arg -y --arg @renzo.johnson/google-search-console-mcp
```

### Hermes

```yaml
mcp_servers:
  com-renzojohnson-google-search-console-mcp:
    command: "npx"
    args: ["-y", "@renzo.johnson/google-search-console-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-renzojohnson-google-search-console-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@renzo.johnson/google-search-console-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-renzojohnson-google-search-console-mcp -t stdio -c npx -a -y @renzo.johnson/google-search-console-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-renzojohnson-google-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-search-console-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-13 (score 65)

First indexed and scored.

## MCP tools (9)

### `ping` (~14 tokens)

Checks server connectivity and auth status

### `gsc_list_sites` (~27 tokens)

Lists all sites (properties) the authenticated user has access to in Google Search Console.

### `gsc_search_analytics` (~231 tokens)

Queries Google Search Console search analytics data: impressions, clicks, CTR, and position for queries, pages, countries, and devices.

Input parameters:

- `aggregation_type` (string): How data is aggregated: auto, byProperty, byPage
- `data_state` (string): Data state: final, all (includes partial data)
- `dimension_filter_groups` (array): Dimension filter groups
- `dimensions` (array): Dimensions to group by: query, page, country, device, searchAppearance, date
- `end_date` (string, required): End date in YYYY-MM-DD format
- `row_limit` (number): Max rows to return (default 1000, max 25000)
- `site_url` (string, required): Site URL as defined in GSC (e.g. "https://example.com/" or "sc-domain:example.com")
- `start_date` (string, required): Start date in YYYY-MM-DD format
- `start_row` (number): Zero-based row offset for pagination
- `type` (string): Search type: web, image, video, news, discover, googleNews

### `gsc_inspect_url` (~103 tokens)

Inspects a URL in Google Search Console. Returns index status, crawl info, mobile usability, and rich results.

Input parameters:

- `inspection_url` (string, required): Full URL to inspect (must be under the site_url property)
- `language_code` (string): Language for issue messages (default: en-US)
- `site_url` (string, required): Site URL as defined in GSC (e.g. "https://example.com/" or "sc-domain:example.com")

### `gsc_list_sitemaps` (~58 tokens)

Lists all sitemaps submitted for a site in Google Search Console.

Input parameters:

- `site_url` (string, required): Site URL as defined in GSC (e.g. "https://example.com/" or "sc-domain:example.com")

### `gsc_add_site` (~66 tokens)

Adds a site to Google Search Console. Use URL prefix (e.g. "https://example.com/") or domain property (e.g. "sc-domain:example.com").

Input parameters:

- `site_url` (string, required): Site URL to add (URL prefix or sc-domain: format)

### `gsc_submit_sitemap` (~54 tokens)

Submits a sitemap URL for a site in Google Search Console.

Input parameters:

- `site_url` (string, required): Site URL as defined in GSC
- `sitemap_url` (string, required): Full URL of the sitemap to submit

### `indexing_notify` (~94 tokens)

Notifies Google to crawl or remove a URL via the Indexing API. Google honours it only for job posting and livestream pages. Destructive (confirm:true): type URL_DELETED.

Input parameters:

- `confirm` (boolean): Must be true for URL_DELETED, which asks Google to drop the URL
- `type` (string): Notification type (default: URL_UPDATED)
- `url` (string, required): Full URL to notify Google about

### `indexing_status` (~37 tokens)

Checks the last crawl/notification status for a URL via the Indexing API.

Input parameters:

- `url` (string, required): URL to check notification status for

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-renzojohnson-google-search-console-mcp/renzo-johnson-google-search-console-mcp#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 65
- 2026-11-19: 65
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 65
- 2026-11-15: 65
- 2026-11-14: 65
- 2026-11-13: 65

## Common questions

### What is the Google Search Console MCP server?

Google Search Console MCP is listed in the public MCP registry as com.renzojohnson/google-search-console-mcp. Search Console MCP server: search analytics, URL inspection, sitemaps and the Indexing API. This page covers its npm package (@renzo.johnson/google-search-console-mcp).

### Is the Google Search Console MCP server safe to use?

Google Search Console MCP scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 9 tools: ping, gsc_list_sites, gsc_search_analytics, gsc_inspect_url, gsc_list_sitemaps, and 4 more. Their descriptions and schemas cost roughly 684 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 21 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.

### What did VerifyMCP test on the Google Search Console MCP server?

VerifyMCP ran 14 checks on Google Search Console MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Google Search Console MCP: Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@renzo.johnson/google-search-console-mcp
- Socket report: https://socket.dev/npm/package/@renzo.johnson/google-search-console-mcp
- Website: https://renzojohnson.com/contributions/google-search-console-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-renzojohnson-google-search-console-mcp/renzo-johnson-google-search-console-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-renzojohnson-google-search-console-mcp/renzo-johnson-google-search-console-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-renzojohnson-google-search-console-mcp/renzo-johnson-google-search-console-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-renzojohnson-google-search-console-mcp/renzo-johnson-google-search-console-mcp
