MCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection
The current version, v0.2.0, was published to the official MCP registry on 2026-09-03. It is distributed as @ni-c/google-search-console-mcp on npm and as the Docker image ghcr.io/ni-c/google-search-console-mcp:0.2.0, filed under Analytics by this index, and declares 11 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using Google Search Console in Claude, Cursor, Gemini CLI, Cline, or Zed? #
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wire
Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.description
passINFOevidence“Normal capability description”via static_description
-
- Semantic screen only - the deterministic conformance probe has not run on this server
-
- Confidence is reported but not yet calibrated (v1)
-
- Screen reads the tool description, not the live behavior
-
- advisory
-
- registry description only no input schema
-
- screen model 8b
-
- The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Screen its description →
That verdict was true at screening time (snapshot 2026-09-03). #
Contracts can change after screening, with no version bump. The gate pins Google Search Console’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for Google Search Console](https://mcpindex.ai/server/io-github-ni-c-google-search-console-mcp) - screening verdict, registry provenance, and contract drift monitoring.
<a href="https://mcpindex.ai/server/io-github-ni-c-google-search-console-mcp">Independent trust record for Google Search Console</a> - screening verdict, registry provenance, and contract drift monitoring.
A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-ni-c-google-search-console-mcp)
<a href="https://mcpindex.ai/server/io-github-ni-c-google-search-console-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-ni-c-google-search-console-mcp" alt="mcpindex verdict" height="20" /></a>
GSC_SERVICE_ACCOUNT_KEY
Service account key as JSON, or base64-encoded JSON. One of the three credential options.
GSC_SERVICE_ACCOUNT_KEY_FILE
Path to a service account key file. Alternative to GSC_SERVICE_ACCOUNT_KEY.
GSC_CLIENT_ID
OAuth2 client id. Use together with GSC_CLIENT_SECRET and GSC_REFRESH_TOKEN.
GSC_CLIENT_SECRET
OAuth2 client secret. All three OAuth2 variables are required together.
GSC_REFRESH_TOKEN
OAuth2 refresh token. All three OAuth2 variables are required together.
GOOGLE_APPLICATION_CREDENTIALS
Path to application default credentials, used when no GSC_ credential is set.
GSC_SITE_URL
Default property, e.g. sc-domain:example.com or https://example.com/ — makes site_url optional
GSC_ALLOWED_SITES
Comma-separated properties this server may touch; anything else is refused
GSC_READ_ONLY
Set to true to register only the read tools (default: false)
GSC_ALLOW_TOOLS
Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)
GSC_DENY_TOOLS
Comma-separated tool names or list_* prefixes to remove from whatever the allow list left
GSC_SERVICE_ACCOUNT_KEY
Service account key as JSON, or base64-encoded JSON. One of the three credential options.
GSC_SERVICE_ACCOUNT_KEY_FILE
Path to a service account key file. Alternative to GSC_SERVICE_ACCOUNT_KEY.
GSC_CLIENT_ID
OAuth2 client id. Use together with GSC_CLIENT_SECRET and GSC_REFRESH_TOKEN.
GSC_CLIENT_SECRET
OAuth2 client secret. All three OAuth2 variables are required together.
GSC_REFRESH_TOKEN
OAuth2 refresh token. All three OAuth2 variables are required together.
GOOGLE_APPLICATION_CREDENTIALS
Path to application default credentials, used when no GSC_ credential is set.
GSC_SITE_URL
Default property, e.g. sc-domain:example.com or https://example.com/ — makes site_url optional
GSC_ALLOWED_SITES
Comma-separated properties this server may touch; anything else is refused
GSC_READ_ONLY
Set to true to register only the read tools (default: false)
GSC_ALLOW_TOOLS
Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)
GSC_DENY_TOOLS
Comma-separated tool names or list_* prefixes to remove from whatever the allow list left
Creator discovery & analytics across YouTube, Instagram, TikTok (30M+) + brand/sponsor intel.
AIOProductOS MCPcom.aioproductos/mcp
AIOProductOS: revenue, feedback, work and analytics on one customer record. 71 tools, 3 apps.
Pensiata - Bulgarian Pension Fund Analyticsio.github.nvasilevv/pensiata
Bulgarian pension fund analytics — NAV data, metrics, rankings, and benchmarks.