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

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

Available components

−2 this week 88 Trust /100

Last scanned (28 minutes ago)

Scores higher than 92% 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 Security93
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects glob 10.5.0, reached via @google-analytics/data > google-gax > rimraf > glob. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 69 of 246 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 14 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
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.

  • 31 Oct 26 −1
    • CVE-2026-118764 affects this package: medium ▼ security
    • CVE-2026-118773 affects this package: medium ▼ security
    • Known CVEs: pass → fail ▼ security
    • Stability: 0.97 → pass security
  • 30 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 +1
    • Stability: 0.97 → pass security
  • 22 Oct 26 +14
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.93 functional
  • 21 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 2.1.3 → 2.1.4 functional
  • 16 Oct 26 +1
    • Stability: 0.97 → pass security
  • 14 Oct 26 +1

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

  • 12 Oct 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 5 Nov 2026 · Analysed npm/search-console-mcp@2.1.4

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.4
Rekor log index 3357103326
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:550fcb47c3c2d44466ba4f1574ac373e1c32b516cfe10d66e7b340504ea7253e817720c21ffc9e45f4d682dcaebda43692da9224a7b3ab7ae464308e8

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-3g3m-2fjr-6pw4 CVE-2026-118773 medium yes
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 246 packages
Packages resolved 246
Deprecated 3
Stale 67
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
accountIdstring–Account ID for add_site or remove
actionstringyesAccount action
emailstring–Optional email filter
siteUrlstring–Site 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
accountIdstring–Specific AdSense account ID (default: auto-select)
modestring–configured = 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
accountIdstring–Specific 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
accountIdstring–Specific AdSense account ID (default: auto-select)
dateRangestring–Preset date range (default: LAST_7_DAYS)
dimensionsarray–Breakdown dimensions
endDatestring–Custom end date YYYY-MM-DD (requires startDate)
metricsarray–Metrics to report (default: earnings, page views, impressions, clicks, RPM)
orderBystring–Sort order as "+METRIC" (ascending) or "-METRIC" (descending), e.g. "-ESTIMATED_EARNINGS"
rowLimitnumber–Max rows to return (default: 100, max: 200)
startDatestring–Custom 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
endDatestring–End date YYYY-MM-DD
metricTypestringyesMetric type
propertyIdstringyesGA4 Property ID
startDatestring–Start date YYYY-MM-DD

No output schema declared.

No examples provided.

analytics_anomalies ~81

Detect search traffic anomalies across Google and Bing.

NameTypeReqDescription
endDatestring–End date YYYY-MM-DD
enginestring–Target search engine (default: all)
siteUrlstringyesThe site property URL
startDatestring–Start date YYYY-MM-DD
thresholdnumber–Sensitivity threshold

No output schema declared.

No examples provided.

analytics_compare ~108

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

NameTypeReqDescription
compareEndDatestring–Comparison end date
compareStartDatestring–Comparison start date
endDatestring–End date YYYY-MM-DD
enginestring–Target search engine (default: all)
modestring–Comparison mode
siteUrlstringyesThe site property URL
startDatestring–Start 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
dimensionsarray–Dimensions: query, page, country, device, searchAppearance, date
endDatestring–End date YYYY-MM-DD
enginestring–Target search engine (default: all)
filtersarray–Filter objects
rowLimitnumber–Row limit
siteUrlstringyesThe site property URL
startDatestring–Start 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
dimensionstring–Comparison dimension
endDatestring–End date YYYY-MM-DD
limitnumber–Result row limit
siteUrlstringyesThe site property URL
startDatestring–Start 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
daysnumber–Lookback window in days (default: 28)
enginestring–Target search engine (default: all)
includePagesboolean–Enrich matched queries with the pages they map to (default: false)
minImpressionsnumber–Ignore 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
enginestring–Target search engine
siteUrlstringyesThe site property URL
typestring–Check type (default: status)
urlstring–URL 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
enginestring–Target search engine (default: google)
hoststring–Host for IndexNow submission
keystring–Key for IndexNow submission
keyLocationstring–Key location URL for IndexNow
methodstring–Submission method (default: standard)
siteUrlstring–The 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
enginestring–Target 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
categoryarray–Lighthouse categories
cwvOnlyboolean–Return Core Web Vitals metrics only
strategystring–Device 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
brandKeywordsarray–Brand keywords for brand_vs_nonbrand analysis
enginestring–Target search engine (default: all)
minImpressionsnumber–Minimum 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
countrystring–Country code
enginestring–Target search engine (default: google)
keywordsarrayyesKeywords to analyze
languagestring–Language code
siteUrlstring–The site property URL
typestring–Analysis type

No output schema declared.

No examples provided.

site_health_check ~57

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

NameTypeReqDescription
enginestring–Target search engine (default: all)
levelstring–Health check depth
siteUrlstring–Optional 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
enginestring–Target 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
enginestring–Target search engine (default: all)
feedUrlstring–Optional 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
enginestring–Target 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
enginestring–Target 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
enginestring–Target search engine (default: all)
siteUrlstringyesThe site property URL

No output schema declared.

No examples provided.

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
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 88 out of 100 on VerifyMCP. We recorded 2 known advisories against 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.

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