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.

Search Console MCP

NPM · SEARCH-CONSOLE-MCP · SCANNED SEP 20

Google Search Console + Bing + GA4 + AdSense — unified SEO intelligence for AI agents.

Available components

0 this week 89 Trust /100
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 Security98
  • 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
  • 70 of 250 dependencies flagged as unhealthy (3 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to saurabhsharma2u/search-console-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 17 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability54
  • 26% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2095 tokens (~69/item across 30 items; 25 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "sitemaps_delete" 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 26 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
Install

How do I install the Search Console MCP server?

Search Console MCP runs locally as an npm package, launched with npx -y 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 · search-console-mcp

# add to Claude Code
claude mcp add saurabhsharma2u-search-console-mcp -- npx -y search-console-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "saurabhsharma2u-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "search-console-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "saurabhsharma2u-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "search-console-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add saurabhsharma2u-search-console-mcp -- npx -y search-console-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "saurabhsharma2u-search-console-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "search-console-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add saurabhsharma2u-search-console-mcp --command npx --arg -y --arg search-console-mcp
# ~/.hermes/config.yaml
mcp_servers:
  saurabhsharma2u-search-console-mcp:
    command: "npx"
    args: ["-y", "search-console-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "saurabhsharma2u-search-console-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "search-console-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add saurabhsharma2u-search-console-mcp -t stdio -c npx -a -y search-console-mcp
// mcp.json
{
  "mcpServers": {
    "saurabhsharma2u-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "search-console-mcp"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1
    • Security disclosure: unverified → pass functional
  • 19 Sept 26 0
    • Security disclosure: pass → unverified functional
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1
    • Security disclosure: unverified → pass functional
  • 12 Sept 26 0
    • Security disclosure: pass → unverified functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

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 20 Sept 2026 · Analysed npm/search-console-mcp@2.1.3

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 saurabhsharma2u/search-console-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/saurabhsharma2u/search-console-mcp/.github/workflows/publish.yml@refs/tags/v2.1.3
Rekor log index 2685423848
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:2122a1d44798744ff405e6b5da749d9561cd72d389959430c33b483d05657405a1a762389cef5eaa92512d922ab0b06267e9e9915b742128ac1ab011e

Background: How many MCP packages publish verified provenance →

Dependencies 250 packages
Packages resolved 250
Deprecated 3
Stale 68
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 25 exposed · ~1,977 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
accounts_manage ~66

Manage Google Search Console service accounts and site permissions.

NameTypeReqDescription
accountIdstringAccount ID for add_site or remove
actionstringyesAccount action
emailstringOptional email filter
siteUrlstringSite URL to add to account

No output schema declared.

No examples provided.

adsense_accounts ~68

List configured AdSense publisher accounts, or discover all publisher accounts the authorized user has access to.

NameTypeReqDescription
accountIdstringSpecific AdSense account ID (default: auto-select)
modestringconfigured = saved accounts; discover = all accessible publisher IDs (default: configured)

No output schema declared.

No examples provided.

adsense_payments_alerts ~44

Outstanding AdSense payments and account alerts (policy issues, payment holds).

NameTypeReqDescription
accountIdstringSpecific AdSense account ID (default: auto-select)

No output schema declared.

No examples provided.

adsense_report ~200

Google AdSense earnings & performance report: estimated earnings, impressions, clicks, CTR and RPM with dimension breakdowns.

NameTypeReqDescription
accountIdstringSpecific AdSense account ID (default: auto-select)
dateRangestringPreset date range (default: LAST_7_DAYS)
dimensionsarrayBreakdown dimensions
endDatestringCustom end date YYYY-MM-DD (requires startDate)
metricsarrayMetrics to report (default: earnings, page views, impressions, clicks, RPM)
orderBystringSort order as "+METRIC" (ascending) or "-METRIC" (descending), e.g. "-ESTIMATED_EARNINGS"
rowLimitnumberMax rows to return (default: 100, max: 200)
startDatestringCustom start date YYYY-MM-DD (requires endDate, overrides dateRange)

No output schema declared.

No examples provided.

analytics_advanced ~78

Google Analytics 4 (GA4) e-commerce, realtime metrics, user behavior, and conversion funnels.

NameTypeReqDescription
endDatestringEnd date YYYY-MM-DD
metricTypestringyesMetric type
propertyIdstringyesGA4 Property ID
startDatestringStart date YYYY-MM-DD

No output schema declared.

No examples provided.

analytics_anomalies ~81

Detect search traffic anomalies across Google and Bing.

NameTypeReqDescription
endDatestringEnd date YYYY-MM-DD
enginestringTarget search engine (default: all)
siteUrlstringyesThe site property URL
startDatestringStart date YYYY-MM-DD
thresholdnumberSensitivity threshold

No output schema declared.

No examples provided.

analytics_compare ~108

Period-over-period search performance comparisons, trends, and traffic drop attributions.

NameTypeReqDescription
compareEndDatestringComparison end date
compareStartDatestringComparison start date
endDatestringEnd date YYYY-MM-DD
enginestringTarget search engine (default: all)
modestringComparison mode
siteUrlstringyesThe site property URL
startDatestringStart date YYYY-MM-DD

No output schema declared.

No examples provided.

analytics_query ~123

Unified search performance query replacing single-dimension tools. Supports queries, pages, countries, devices, and search appearances.

NameTypeReqDescription
dimensionsarrayDimensions: query, page, country, device, searchAppearance, date
endDatestringEnd date YYYY-MM-DD
enginestringTarget search engine (default: all)
filtersarrayFilter objects
rowLimitnumberRow limit
siteUrlstringyesThe site property URL
startDatestringStart date YYYY-MM-DD

No output schema declared.

No examples provided.

compare_engines ~79

Cross-engine performance matrix comparing Google Search Console vs Bing Webmaster Tools.

NameTypeReqDescription
dimensionstringComparison dimension
endDatestringEnd date YYYY-MM-DD
limitnumberResult row limit
siteUrlstringyesThe site property URL
startDatestringStart date YYYY-MM-DD

No output schema declared.

No examples provided.

diagnostics ~27

Run connectivity diagnostics for all connected accounts. Use this to troubleshoot '0 results' or authentication issues.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

genai_query_insights ~167

Detect likely generative-AI / AI-Mode / conversational fanout queries across Google and Bing. Because neither search engine exposes generative-AI citation data via its public API yet, this matches heuristic patterns (prompt verbs, follow-ups, conversational phrasing) on regular query-level performance data; it is an undercount, not an official report.

NameTypeReqDescription
daysnumberLookback window in days (default: 28)
enginestringTarget search engine (default: all)
includePagesbooleanEnrich matched queries with the pages they map to (default: false)
minImpressionsnumberIgnore queries with fewer impressions than this (default: 1)
siteUrlstringyesThe site property URL

No output schema declared.

No examples provided.

get_started ~38

Start here. Returns a complete map of this server's capabilities, active platforms, and recommended workflows. Call this once at the beginning of any session.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

indexing_status ~70

Check notification status for Google Indexing API or remaining daily Bing submission quota.

NameTypeReqDescription
enginestringTarget search engine
siteUrlstringyesThe site property URL
typestringCheck type (default: status)
urlstringURL to check status for

No output schema declared.

No examples provided.

indexing_submit ~118

Submit URL(s) for indexing via Google Indexing API, Bing URL submission, or IndexNow protocol.

NameTypeReqDescription
enginestringTarget search engine (default: google)
hoststringHost for IndexNow submission
keystringKey for IndexNow submission
keyLocationstringKey location URL for IndexNow
methodstringSubmission method (default: standard)
siteUrlstringThe site property URL
urlsarrayyesList of URLs to submit

No output schema declared.

No examples provided.

inspection_inspect ~65

Inspect indexing, canonical, and crawl status for single or batch URLs on Google or Bing.

NameTypeReqDescription
enginestringTarget search engine (default: all)
siteUrlstringyesThe site property URL
urlsarrayyesList of URLs to inspect

No output schema declared.

No examples provided.

pagespeed_analyze ~70

Run PageSpeed Insights & Core Web Vitals performance analysis for a page.

NameTypeReqDescription
categoryarrayLighthouse categories
cwvOnlybooleanReturn Core Web Vitals metrics only
strategystringDevice strategy
urlstringyesThe URL to analyze

No output schema declared.

No examples provided.

schema_validate ~43

Validate structured data (JSON-LD, Microdata, RDFa) for a given webpage URL.

NameTypeReqDescription
urlstringyesThe webpage URL to validate structured markup for

No output schema declared.

No examples provided.

seo_audit ~102

Specialized SEO intelligence analysis (recommendations, quick wins, cannibalization, striking distance, lost queries, low CTR, brand vs nonbrand).

NameTypeReqDescription
brandKeywordsarrayBrand keywords for brand_vs_nonbrand analysis
enginestringTarget search engine (default: all)
minImpressionsnumberMinimum impressions threshold
siteUrlstringyesThe site property URL
typestringyesAudit analysis type

No output schema declared.

No examples provided.

seo_keywords_research ~86

Keyword performance stats, related query expansion, and search volume estimates.

NameTypeReqDescription
countrystringCountry code
enginestringTarget search engine (default: google)
keywordsarrayyesKeywords to analyze
languagestringLanguage code
siteUrlstringThe site property URL
typestringAnalysis type

No output schema declared.

No examples provided.

site_health_check ~57

Comprehensive health audit across Google Search Console and Bing Webmaster Tools.

NameTypeReqDescription
enginestringTarget search engine (default: all)
levelstringHealth check depth
siteUrlstringOptional specific site URL

No output schema declared.

No examples provided.

sitemaps_delete ~62

Delete a sitemap from Google Search Console or Bing Webmaster Tools.

NameTypeReqDescription
enginestringTarget search engine (default: all)
feedUrlstringyesThe sitemap feed URL to delete
siteUrlstringyesThe site property URL

No output schema declared.

No examples provided.

sitemaps_list ~61

List submitted XML sitemaps and status for a site.

NameTypeReqDescription
enginestringTarget search engine (default: all)
feedUrlstringOptional specific sitemap feed URL
siteUrlstringyesThe site property URL

No output schema declared.

No examples provided.

sitemaps_submit ~66

Submit a new XML sitemap to Google Search Console and/or Bing Webmaster Tools.

NameTypeReqDescription
enginestringTarget search engine (default: all)
feedUrlstringyesThe XML sitemap feed URL to submit
siteUrlstringyesThe site property URL

No output schema declared.

No examples provided.

sites_list ~39

List verified web properties across Google Search Console, Bing Webmaster Tools, or GA4.

NameTypeReqDescription
enginestringTarget search engine (default: all)

No output schema declared.

No examples provided.

sites_manage ~59

Add or delete a web property from Google Search Console or Bing Webmaster Tools.

NameTypeReqDescription
actionstringyesAction to perform
enginestringTarget search engine (default: all)
siteUrlstringyesThe site property URL

No output schema declared.

No examples provided.

Common questions

What is the Search Console MCP server?

Search Console MCP is listed in the public MCP registry as io.github.saurabhsharma2u/search-console-mcp. Google Search Console + Bing + GA4 + AdSense, unified SEO intelligence for AI agents. This page covers its npm package (search-console-mcp).

Is the Search Console MCP server safe to use?

Search Console MCP scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.

What tools does the Search Console MCP server expose?

Search Console MCP exposes 25 tools: get_started, sites_list, sites_manage, accounts_manage, sitemaps_list, and 20 more. Their descriptions and schemas cost roughly 1,977 tokens of context every time the server is loaded.

Is the Search Console MCP server still maintained?

Search Console MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Search Console MCP server under?

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.