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

NPM · @RENZO.JOHNSON/GOOGLE-SEARCH-CONSOLE-MCP

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

0 this week 65 Trust /100

Last scanned (20 hours ago)

Scores higher than 37% of npm servers

Category Marketing and SEO

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 684 tokens (~76/item across 9 items; 9 tools + 0 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 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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

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.

What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 13 Nov 26 65

    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 21 Nov 2026 · Analysed npm/@renzo.johnson/google-search-console-mcp@26.11.14

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~684 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_add_site ~66

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

NameTypeReqDescription
site_urlstringyesSite URL to add (URL prefix or sc-domain: format)

No output schema declared.

No examples provided.

gsc_inspect_url ~103

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

NameTypeReqDescription
inspection_urlstringyesFull URL to inspect (must be under the site_url property)
language_codestring–Language for issue messages (default: en-US)
site_urlstringyesSite URL as defined in GSC (e.g. "https://example.com/" or "sc-domain:example.com")

No output schema declared.

No examples provided.

gsc_list_sitemaps ~58

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

NameTypeReqDescription
site_urlstringyesSite URL as defined in GSC (e.g. "https://example.com/" or "sc-domain:example.com")

No output schema declared.

No examples provided.

gsc_list_sites ~27

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gsc_search_analytics ~231

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

NameTypeReqDescription
aggregation_typestring–How data is aggregated: auto, byProperty, byPage
data_statestring–Data state: final, all (includes partial data)
dimension_filter_groupsarray–Dimension filter groups
dimensionsarray–Dimensions to group by: query, page, country, device, searchAppearance, date
end_datestringyesEnd date in YYYY-MM-DD format
row_limitnumber–Max rows to return (default 1000, max 25000)
site_urlstringyesSite URL as defined in GSC (e.g. "https://example.com/" or "sc-domain:example.com")
start_datestringyesStart date in YYYY-MM-DD format
start_rownumber–Zero-based row offset for pagination
typestring–Search type: web, image, video, news, discover, googleNews

No output schema declared.

No examples provided.

gsc_submit_sitemap ~54

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

NameTypeReqDescription
site_urlstringyesSite URL as defined in GSC
sitemap_urlstringyesFull URL of the sitemap to submit

No output schema declared.

No examples provided.

indexing_notify ~94

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.

NameTypeReqDescription
confirmboolean–Must be true for URL_DELETED, which asks Google to drop the URL
typestring–Notification type (default: URL_UPDATED)
urlstringyesFull URL to notify Google about

No output schema declared.

No examples provided.

indexing_status ~37

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

NameTypeReqDescription
urlstringyesURL to check notification status for

No output schema declared.

No examples provided.

ping ~14

Checks server connectivity and auth status

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

npm · @renzo.johnson/google-search-console-mcp

# add to Claude Code
claude mcp add com-renzojohnson-google-search-console-mcp -- npx -y @renzo.johnson/google-search-console-mcp
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.