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

NPM · @DIGESTSEO/MCP-GSC

Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics.

Available components

npm · @digestseo/mcp-gsc 50
0 this week 50 Trust /100

Last scanned (58 minutes ago)

Scores higher than 29% 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 Security99
  • 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
  • 43 of 268 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 AKzar1el/mcp-gsc). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 8 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →

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.

  • 27 Oct 26 0
    • Package version: 0.4.39 → 0.4.40 functional
  • 26 Oct 26 +3
    • CVE-2026-109924 no longer affects this package ▲ security
    • CVE-2026-109869 no longer affects this package ▲ security
    • CVE-2026-109841 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
    • Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
    • Package version: 0.4.38 → 0.4.39 functional
  • 25 Oct 26 0
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.4.37 → 0.4.38 functional
  • 24 Oct 26 +2
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-109869 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-109869 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-111767 no longer affects this package ▲ security
    • CVE-2026-104850 no longer affects this package ▲ security
    • CVE-2026-111768 no longer affects this package ▲ security
    • CVE-2026-111771 no longer affects this package ▲ security
    • CVE-2026-111769 no longer affects this package ▲ security
    • CVE-2026-111770 no longer affects this package ▲ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects undici 7.29.1, reached via wrangler > miniflare > undici. A fixed version is available. security
    • Package version: 0.4.36 → 0.4.37 functional
  • 21 Oct 26 −2
    • CVE-2026-111770 affects this package: high ▼ security
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects @modelcontextprotocol/server 2.0.0, a direct dependency. A fixed version is available. security
  • 12 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 11 Oct 26 −4
    • CVE-2026-104850 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
    • Security disclosure: pass → unverified ▼ functional
  • 30 Sept 26 0
    • CVE-2026-85024 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
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 5 Nov 2026 · Analysed npm/@digestseo/mcp-gsc@0.4.40

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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo AKzar1el/mcp-gsc
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/AKzar1el/mcp-gsc/.github/workflows/publish-npm.yml@refs/tags/v0.4.40
Rekor log index 3521404323
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:61fd88dec9cc15fba7ed4ba4bde58e5d11f20edb853821351d4b3c87061ddc8cdb298c3b2c2ebd176d07f0685768d604397b13cc37b3ee71d47c69c1b

Background: How many MCP packages publish verified provenance →

Dependencies 268 packages
Packages resolved 268
Stale 43
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

Install

How do I install the Google Search Console MCP server?

Google Search Console runs locally as an npm package, launched with npx -y @digestseo/mcp-gsc. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @digestseo/mcp-gsc

# add to Claude Code
claude mcp add akzar1el-mcp-gsc -- npx -y @digestseo/mcp-gsc
Common questions

What is the Google Search Console MCP server?

Google Search Console is an MCP server listed in the public MCP registry as io.github.AKzar1el/mcp-gsc. Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics. This page covers its npm package (@digestseo/mcp-gsc).

Is the Google Search Console MCP server safe to use?

Google Search Console scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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.

Is the Google Search Console MCP server still maintained?

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 Google Search Console MCP server under?

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