Google Search Console Connector
NPM · GOOGLE-SEARCH-CONSOLE-CONNECTOR
Google Search Console: search analytics, CSV reports, URL inspection, sitemaps, site verification.
Available components
Last scanned (17 hours ago)
Scores higher than 37% of npm servers
Category Marketing and SEO
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
- 32 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1424 tokens (~79/item across 18 items; 18 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 Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 72% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 19 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.
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 Oct 26 +25
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.86 ▲ functional
- 19 Oct 26 44
First indexed and scored.
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 4 Nov 2026 · Analysed npm/google-search-console-connector@0.1.3
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 104 packages
| Packages resolved | 104 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
gsc_add_annotation Add chart note ~65
Add a dated note to this project's performance chart, e.g. after deploying SEO changes ('Rewrote service page titles'). Shown in the dashboard so changes can be matched to traffic movements.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Default today |
| text | string | yes | – |
No output schema declared.
No examples provided.
gsc_add_site Add property ~53
Add a property to Search Console for the connected account. It stays unverified until gsc_verify_site succeeds.
| Name | Type | Req | Description |
|---|---|---|---|
| siteUrl | string | yes | 'https://example.com/' or 'sc-domain:example.com' |
No output schema declared.
No examples provided.
gsc_connect Connect Google Search Console ~45
Open the Connect page in the user's browser: Google Cloud setup, Google sign-in, and choosing this project's property. Waits until the user finishes (up to 10 minutes).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gsc_delete_sitemap Delete sitemap ~79
Remove a sitemap from the property in Search Console (does not touch the file on the website).
| Name | Type | Req | Description |
|---|---|---|---|
| feedpath | string | yes | – |
| siteUrl | string | – | Property: 'sc-domain:example.com' (domain property) or 'https://example.com/' (URL-prefix, trailing slash). Defaults to the project's linked property. |
No output schema declared.
No examples provided.
gsc_disconnect Disconnect Google ~22
Revoke this machine's Google access token and delete it locally.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gsc_export_report Export Search Console reports ~158
Download Search Console reports in one step: Dates, Queries, Pages, Countries, Devices, Search appearance, Query-page pairs and Sitemaps as CSV (same columns as Search Console's Export, plus previous-period comparison), report.json, and summary.md written for you to read next. Saved to .gsc-reports/ in the project (added to .gitignore).
| Name | Type | Req | Description |
|---|---|---|---|
| allSites | boolean | – | Export every property the account can access |
| days | integer | – | Default 28 |
| siteUrl | string | – | Property: 'sc-domain:example.com' (domain property) or 'https://example.com/' (URL-prefix, trailing slash). Defaults to the project's linked property. |
| type | string | – | – |
No output schema declared.
No examples provided.
gsc_get_verification_token Get verification token ~75
Get the ownership verification token. META returns a <meta> tag for the site's <head> (URL-prefix properties). FILE returns an HTML file name/content to serve at the site root. DNS_TXT is required for sc-domain properties.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | – |
| siteUrl | string | yes | – |
No output schema declared.
No examples provided.
gsc_inspect_url Inspect URL ~89
URL Inspection: index status, coverage, last crawl, canonical and rich results for one URL in the property.
| Name | Type | Req | Description |
|---|---|---|---|
| siteUrl | string | – | Property: 'sc-domain:example.com' (domain property) or 'https://example.com/' (URL-prefix, trailing slash). Defaults to the project's linked property. |
| url | string | yes | Fully-qualified URL that belongs to the property |
No output schema declared.
No examples provided.
gsc_link_project Link project to property ~53
Save which Search Console property this website project uses (writes .gsc-connect.json in the project root; contains no secrets).
| Name | Type | Req | Description |
|---|---|---|---|
| siteUrl | string | yes | Property URL exactly as gsc_list_sites returns it |
No output schema declared.
No examples provided.
gsc_list_sitemaps List sitemaps ~72
Sitemaps submitted for the property, with status, errors, warnings and last download time.
| Name | Type | Req | Description |
|---|---|---|---|
| siteUrl | string | – | Property: 'sc-domain:example.com' (domain property) or 'https://example.com/' (URL-prefix, trailing slash). Defaults to the project's linked property. |
No output schema declared.
No examples provided.
gsc_list_sites List properties ~24
List Search Console properties the connected account can access, with permission level.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gsc_open_dashboard Open the GSC dashboard ~32
Open the local Search Console dashboard (performance, queries, pages, opportunities, indexing) in the user's browser.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gsc_performance_summary Performance summary ~119
Totals for a period compared with the previous period of equal length, plus top queries and pages. A good first call for 'how is the site doing?'.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Period length in days, ending yesterday. Default 28. |
| siteUrl | string | – | Property: 'sc-domain:example.com' (domain property) or 'https://example.com/' (URL-prefix, trailing slash). Defaults to the project's linked property. |
| top | integer | – | Top queries/pages to include. Default 10. |
No output schema declared.
No examples provided.
gsc_search_analytics Search analytics query ~230
Query Search Console performance data (clicks, impressions, CTR, position). Data is available for the last 16 months and usually lags 2–3 days. CTR is returned as a fraction.
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | array | – | 'hour' returns hourly rows for the last ~10 days (dataState hourly_all). Discover and Google News don't support 'query'. |
| endDate | string | – | Default: yesterday |
| filters | array | – | ANDed together. Regex operators use RE2 syntax. |
| queryType | string | – | Uses the project's brand terms (gsc_set_brand_terms) |
| rowLimit | integer | – | Default 100 |
| siteUrl | string | – | Property: 'sc-domain:example.com' (domain property) or 'https://example.com/' (URL-prefix, trailing slash). Defaults to the project's linked property. |
| startDate | string | – | Default: 28 days ago |
| startRow | integer | – | – |
| type | string | – | Default web. Web includes AI Overviews and AI Mode; the API can't separate them. |
No output schema declared.
No examples provided.
gsc_set_brand_terms Set brand terms ~60
Set the words that make a query 'branded' (business name, product names, common misspellings). Enables branded vs non-branded analysis in gsc_search_analytics, reports and the dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| terms | array | yes | – |
No output schema declared.
No examples provided.
gsc_status Connection status ~27
Show whether Google is connected, which account, and which property this project is linked to.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gsc_submit_sitemap Submit sitemap ~83
Submit (or resubmit) a sitemap URL for the property.
| Name | Type | Req | Description |
|---|---|---|---|
| feedpath | string | yes | e.g. https://example.com/sitemap.xml |
| siteUrl | string | – | Property: 'sc-domain:example.com' (domain property) or 'https://example.com/' (URL-prefix, trailing slash). Defaults to the project's linked property. |
No output schema declared.
No examples provided.
gsc_verify_site Verify ownership ~52
Ask Google to check the verification token placed by the chosen method. Run after deploying the meta tag / file or adding the DNS record.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | – |
| siteUrl | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Google Search Console Connector MCP server?
Google Search Console Connector runs locally as an npm package, launched with npx -y google-search-console-connector. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · google-search-console-connector
claude mcp add malaysherasia-ai-google-search-console-connector -- npx -y google-search-console-connector
What is the Google Search Console Connector MCP server?
Google Search Console Connector is an MCP server listed in the public MCP registry as io.github.malaysherasia-ai/google-search-console-connector. Google Search Console: search analytics, CSV reports, URL inspection, sitemaps, site verification. This page covers its npm package (google-search-console-connector).
Is the Google Search Console Connector MCP server safe to use?
Google Search Console Connector scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Connector MCP server expose?
Google Search Console Connector exposes 18 tools: gsc_connect, gsc_open_dashboard, gsc_status, gsc_disconnect, gsc_list_sites, and 13 more. Their descriptions and schemas cost roughly 1,338 tokens of context every time the server is loaded.
Is the Google Search Console Connector MCP server still maintained?
Google Search Console Connector is still listed as active in the MCP registry. We last reached this channel on 4 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 Connector MCP server under?
Google Search Console Connector declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.