io.github.sarahpark/google-search-console
NPM · @SARAHPARK/GOOGLE-SEARCH-CONSOLE-MCP
Google Search Console MCP server — search analytics, URL inspection, and sitemaps
Available components
Last scanned (19 hours ago)
Scores higher than 65% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 40 of 118 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- 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 45 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 356 tokens (~89/item across 4 items; 4 tools + 0 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −2
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Package version: 1.0.1 → 1.1.0 functional
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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/@sarahpark/google-search-console-mcp@1.1.0
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 →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 118 packages
| Packages resolved | 118 |
|---|---|
| Deprecated | 1 |
| Stale | 39 |
| 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 →
inspect_url ~61
Inspect a URL to check its indexing status, crawl info, and any issues Google found.
| Name | Type | Req | Description |
|---|---|---|---|
| inspectionUrl | string | yes | The full URL to inspect (must belong to the site) |
| siteUrl | string | yes | Site URL as it appears in Search Console |
No output schema declared.
No examples provided.
list_sitemaps ~40
List all sitemaps submitted for a site in Google Search Console.
| Name | Type | Req | Description |
|---|---|---|---|
| siteUrl | string | yes | Site URL as it appears in Search Console |
No output schema declared.
No examples provided.
list_sites ~23
List all sites (properties) you have access to in Google Search Console.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_analytics ~232
Query search analytics data from Google Search Console. Returns clicks, impressions, CTR, and position for your site.
| Name | Type | Req | Description |
|---|---|---|---|
| countryFilter | string | – | Filter by country (ISO 3166-1 alpha-3, e.g. USA, GBR) |
| deviceFilter | string | – | Filter by device type |
| dimensions | string | – | Comma-separated dimensions: query, page, country, device, searchAppearance, date |
| endDate | string | yes | End date in YYYY-MM-DD format |
| pageFilter | string | – | Filter by page URL. Prefix with regex: for regex matching. |
| queryFilter | string | – | Filter by search query. Prefix with regex: for regex matching. |
| rowLimit | number | – | Max rows to return (default 100, max 25000) |
| searchType | string | – | Type of search results to query |
| siteUrl | string | yes | Site URL exactly as it appears in Search Console (e.g. https://example.com/ or sc-domain:example.com) |
| startDate | string | yes | Start date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
How do I install the io.github.sarahpark/google-search-console MCP server?
io.github.sarahpark/google-search-console runs locally as an npm package, launched with npx -y @sarahpark/google-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 · @sarahpark/google-search-console-mcp
claude mcp add sarahpark-google-search-console -- npx -y @sarahpark/google-search-console-mcp
What is the io.github.sarahpark/google-search-console MCP server?
io.github.sarahpark/google-search-console is an MCP server listed in the public MCP registry as io.github.sarahpark/google-search-console. Google Search Console MCP server, search analytics, URL inspection, and sitemaps. This page covers its npm package (@sarahpark/google-search-console-mcp).
Is the io.github.sarahpark/google-search-console MCP server safe to use?
io.github.sarahpark/google-search-console scores 80 out of 100 on VerifyMCP. We recorded 2 known advisories against 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 io.github.sarahpark/google-search-console MCP server expose?
io.github.sarahpark/google-search-console exposes 4 tools: list_sites, search_analytics, inspect_url, list_sitemaps. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.
Is the io.github.sarahpark/google-search-console MCP server still maintained?
io.github.sarahpark/google-search-console 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 io.github.sarahpark/google-search-console MCP server under?
io.github.sarahpark/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.